Okay, I finally got around to putting the ClosedSRS VB6 source onto SourceForge. Take a look at the CSControl_VB6Code file at http://sourceforge.net/project/showfiles.php?group_id=82278. Specifically, pay attention to the SRSComm class. This is where all encrypted communication occurs. (It actually just calls functions in the C++ SRSHelp DLL. All socket/crypto operations take place within this DLL, as it was easier to do it in VC back then.)
If I were writting the control in Windows nowadays, I'd do the whole thing in .Net. The trickiest part would be getting the crypto working. Once this part is done, its just a matter of slogging around with all the SRS commands. Have fun.. ----- Original Message ----- From: "Lynn W. Taylor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 23, 2003 4:52 PM Subject: Re: ASP.NET DEVELOPRS error: 405 Method Not Allowed I haven't spent a whole bunch of time on this, but maybe this will help.... I don't think the problem is Blowfish, I think it is CBC. Blowfish is a block cypher, and OpenSRS needs a streaming cypher. CBC is a technique to turn block cyphers into streaming cyphers. >From what I've read, there appears to be two flavors of CBC: the "real world standard" one, and the one implemented in the PERL Crypt:CBC library. There are a couple of other differences, but there are third-party documents that cover them. As far as I remember, they had to do with how keys were generated for the cypher. -- Lynn On Sun, 23 Nov 2003 18:23:43 -0600, [EMAIL PROTECTED] wrote: > I feel the same way. :( > > The really said part is that Blowfish was released as an > open standard and so it's trivial to get your hands on > source for virtually any language / platform. Tucows > really needs to write up and provide a nice clean white > paper on their unique Blowfish "tweaks" as well as provide > test vectors using a trivial key so you can test your > code. > > >>On Sun, 23 Nov 2003 12:06:28 -0800, >>[EMAIL PROTECTED] wrote: >> Well I looked at the ClosedSRS project on >>sourceforge.net. It looks like >> all the main connection is done through the .dll file >>and does not help out >> in any way. I would not want to code around a DLL that >>someone else made, >> it would cause alot of headaches in the future.
