Re: Blowfish.e versus decimal points

new topic     » goto parent     » topic index » view thread      » older message » newer message

Greg Haberek wrote:
> > 
> > There is no pattern I can discern (although I'm sure there is one).  I can
> > have
> > a perfectly acceptable sequence and then I change the init key or change  a
> > few bytes and it won't decrypt.  I never seem to have problems encrypting. 
> > It is always coming back the other direction that creates the problem.
> 
> I ran into the same issue, too. I think it was because I was reading/writing
> files in text mode. You have to open your files as "rb" or "wb" because the
> encrypted data is binary, not text. That should fix your issue. Though I had
> that issue quite a while ago, and never made note of how to fix it. So I could
> be wrong...

You are not wrong.  I was writing everything with binary, but I was reading one
file with text.  I thought it wouldn't matter because I had used a text editor
that allows long lines and all of the data (the entire sequence) was on one line.
 Or so I thought.

> P.S. I found a couple other bugs in blowfish.e, in the wrappers for the file
> routines:
> 
> }}}
<eucode>
> -- line 523, change this:
>   else
>       call_proc(oldprint, {fn, st, x})
>   end if
> -- to this:
>   else
>       call_proc(oldprintf, {fn, st, x})
>   end if
> 
> -- at line 535, change this:
>   integer found
>   sequence line, st
>       found = find(fn, filefns)
> -- to this:
>   integer found
>   sequence line
>   object st
>       found = find(fn, filefns)
> </eucode>
{{{


Thanks.  I'll put this on my list of things to update on my version.

Mike

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu