Re: Encryption Code Problem
Re: Encryption Code Problem
- Subject: Re: Encryption Code Problem
- From: "Jonathan 'Wolf' Rentzsch" <email@hidden>
- Date: Tue, 3 Jun 2003 09:44:33 -0500
Jonathan Fleming, email@hidden, wrote:
>Can anyone tell if I'm doing something wrong here. I had this working with
>an OpenBase database but I've recently moved over to MSSQLServer2000 and now
>can not get past my login possibly... no probably because my encryption code
>is not encoding correctly. If I turn off the encryption code and enter a
>normal text password i can get past the login as normal.
...
>In the database EOModel I have added to the connection dictionary
>
>databaseEncoding: ISO Latin-1
>The password column of the database & EOModel accepts 255 varchar, enough
>i'm sure to cover the encrypted text
I suspect your binary stream is not surviving the roundtrip to the
database. Try Hex-encoding the binary stream first before storing it to
the database, and decoding it upon retrival. That way you're only storing
ASCII characters, which is much more likely to work.
Both Apache Jakarta and BouncyCastle have hex encoder/decoder available.
Also, Raphael Szwarc wrote one and posted it:
<http://www.wodeveloper.com/omniLists/webobjects-dev/2002/July/msg00157.htm
l>
.......................................................
Jonathan 'Wolf' Rentzsch http://rentzsch.com
Red Shed Software http://redshed.net (847) 584-7465
PGP: b2af 1a09 f881 ebde c9d6 c4d2 c04f a3c0 3ec5 d5f2
"better" necessarily means "different"
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.