Re: portability of emelFM2 encrypted files

Hello Tom,

On 6/3/08, tpgww@xxxxxxxxxxx <tpgww@xxxxxxxxxxx> wrote:
> In general, no. The de/en-cryption algorithm is the same, but different 
> information may be included in the header, and the [de]compression process 
> may be different.
>
>  Originally, it was intended to enable compatibility, via a build-time define:
>  #define TC_COMPATIBLE
>  However this has never been finished or tested. Probably no big deal to do 
> so, if anyone really wants it.
>
It would be quite handy for it to be so. How should I best approach
testing this? Did you make additional changes to emel's source, or is
it enough to uncomment the line?


>  The original inspiration was tinycrypt v. 0.4, and no attempt has been made 
> to conform to any changes in later versions. Though I'd like to think there's 
> nothing incompatible, or else prior tinycrypt encryptions would be useless.
>
I have just managed to build tinycrypt_0.4. I will also check whether
tinycrypt_0.41 compiles, and whether emel-encrypted files are
compatible with this one.

Liviu


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: