Xref: utzoo comp.unix.questions:12753 comp.unix.microport:3109 sci.crypt:1793
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!rutgers!bellcore!texbell!bigtex!pmafire!dave
From: dave@pmafire.UUCP (Dave Remien)
Newsgroups: comp.unix.questions,comp.unix.microport,comp.unix.i386,sci.crypt
Subject: Re: Decrypting Files Encrypted on Another Machine
Summary: Try swapping bytes with dd
Keywords: crypt portable
Message-ID: <621@pmafire.UUCP>
Date: 8 Apr 89 16:39:17 GMT
References: <198@rancho.uucp> <4119@stiatl.UUCP>
Reply-To: dave@pmafire.UUCP (Dave Remien)
Distribution: usa
Organization: WINCO, INEL, Idaho
Lines: 16

In article <4119@stiatl.UUCP= todd@stiatl.UUCP (Todd Merriman) writes:
=In article <198@rancho.uucp= rock@rancho.uucp (Rock Kent) writes:
==I have been unsuccessful in taking files which have been encrypted on
==an NCR Tower using crypt(1) and decrypting them on a microport Sys
==V/386 system. 
=
=
=More than likely, integers are being stored in the encrypted file if
=the encrypting program is not treating the input and output files as
=byte streams.  Due to differences in architectures between the Tower
=(68000, I think) and the 386, integers are stored with a different
=byte ordering.  You need a crypt/decrypt that is specifically
=non-architecture dependent.

It's a cheap shot, but you could try dd'ing the file to swap bytes (dd
conv=swab), then try crypt on it again.