AES, counter mode, etc.

When I looked at the AES API, it looked like there was no way to specify a block size independently of the key size. Is that intentional? Additionally, with respect to counter mode, it might be best to implement external to the EVP proper interface, just like HMAC. There are a few issues I

'make test' problem in openssl-0.9.7-stable-SNAP-20020213

The 'make test' target is assuming that 'openssl.cnf' already exists in the location where OpenSSL is to be installed. This causes the test to fail in our environment where each new revision of a piece of software is given its own location. 'Make report' results for one system (Solaris 2.5.1)

Re: OpenSSL (openssl-0.9.1c)

On Thu, Feb 14, 2002 at 04:16:40PM +0100, Richard Levitte - VMS Whacker wrote: From: Khan Alamgir [EMAIL PROTECTED] akh Please help! Use a more modern OpenSSL. The current release is 0.9.6c. And call SSL_library_init() :-) Lutz -- Lutz Jaenicke [EMAIL

Re: OpenSSL Makefiles - SUGGESTION

On Thu, Feb 07, 2002 at 07:17:50AM -0500, Saju Paul Panikulam wrote: It would be nice to have a paragraph in the Makefiles to remove the TAB (^I) characters from the OpenSSL source and header files. The debugger on the platform that we use does not handle the TABs very well. Had to write a

Re: cvs commit: openssl/crypto/err err.c

Bodo Moeller wrote: On Thu, Feb 14, 2002 at 02:42:36PM +0100, [EMAIL PROTECTED] wrote: Log: For some reason, getting the topmost error was done the same way as getting the bottommost one. I hope I understood correctly how this should be done. It seems to work when running

Re: 'make test' problem in openssl-0.9.7-stable-SNAP-20020213

From: Dawn Whiteside [EMAIL PROTECTED] dwhitesi The 'make test' target is assuming that 'openssl.cnf' already exists dwhitesi in the location where OpenSSL is to be installed. This causes the dwhitesi test to fail in our environment where each new revision of a piece dwhitesi of software is

Re: cvs commit: openssl/crypto/err err.c

On Fri, Feb 15, 2002 at 10:55:13AM +, Ben Laurie wrote: This fix for err.c is correct. But evp_test.c should never have called OPENSSL_config() because OPENSSL_config() uses the configuration file found in an OpenSSL *installation*. If we want to use a configuration file during 'make

Re: OpenSSL and ASP

Warning: loads of Win32-specific information inside. Proceed at your own risk! If by making it run via ASP/IIS you mean having it accessible from Visual Basic/VBScript I'm afraid there's quite a bit of manual tweaking that will have to be done. In order for C functions to be at all usable from

Re: OpenSSL and ASP

here a resume some points last april that I found while trying to compile the library. - The basic approach is to compile the whole stuff with the /Gz option in order not to modify the 3000 exported function prototypes. - All main routines need a __cdecl main The #define for MAIN, all

Re: OpenSSL and ASP

From: Oscar Jacobsson [EMAIL PROTECTED] oscar Hope this gives you a few ideas on how to proceed. I might be able to oscar find some time to look into making OpenSSL VB-friendly, but I can't make oscar any promises at present. :-/ Suggestion: there are packages out there that supply interfaces

Re: cvs commit: openssl/crypto/err err.c

Bodo Moeller wrote: On Fri, Feb 15, 2002 at 10:55:13AM +, Ben Laurie wrote: This fix for err.c is correct. But evp_test.c should never have called OPENSSL_config() because OPENSSL_config() uses the configuration file found in an OpenSSL *installation*. If we want to use a

Re: cvs commit: openssl/crypto/engine hw_sureware.c

Hmm. You did this with a different name from me (idx instead of index_) - isn't that going to be irritating? [EMAIL PROTECTED] wrote: steve 14-Feb-2002 19:46:16 Modified:crypto/engine Tag: OpenSSL_0_9_7-stable hw_sureware.c Log: Fix warnings: #if out some unused

Re: cvs commit: openssl/crypto/engine hw_sureware.c

Ben Laurie wrote: Hmm. You did this with a different name from me (idx instead of index_) - isn't that going to be irritating? I hadn't realised someone else had come across this. It should be consistent I suppose. Personally I always find variable names with appended underscores a little

zencod ENGINE for OpenSSL-SNAP-0.9.7-20020214

Title: zencod ENGINE for OpenSSL-SNAP-0.9.7-20020214 Hi all, My company (zencod) has developped a crypto accelerator which should provide: - asymetric computations: RSA, DSA, DH - random generation - digest functions: SHA1, MD5 - cipher operations: DES, RC4 So we have coded an ENGINE

RE: OpenSSL and ASP

Thanks a bunch for the help and the insight. Hope it isn't too offensive to the list as a whole for me to do this publicly, but I am in awe of the whole experience. This is my first attempt to participate in an Open Source forum and you guys have been way helpful and prompt in your replies.

Re: AES, counter mode, etc.

Thus spake John Viega: When I looked at the AES API, it looked like there was no way to specify a block size independently of the key size. Is that intentional? The NIST FIPS specifies AES with a 128-bit block size. Rijndael can be used in many other ways, but there is a significant

This is a test

Please ignore this message. I'm testing a bug database for OpenSSL so hopefully we'll be able to better keep track of bug reports... __ OpenSSL Project http://www.openssl.org Development Mailing

Re: EVP macros for AES

Thus spake Richard Levitte - VMS Whacker: From: Stephen Sprunk [EMAIL PROTECTED] stephen After implementing CBC, CFB, OFB, and CTR for AES (mostly plagiarized stephen from IDEA), I'm beginning to wonder why we have 40 different stephen implementations of the exact same algorithms in the

Re: EVP macros for AES

Stephen Sprunk wrote: Thus spake Richard Levitte - VMS Whacker: The current state is EAY legacy. His idea was that one should be able to pick out any of the algorithm directories and create a separate library for them (the old libdes is actually exactly the same as crypto/des/).

Re: AES, counter mode, etc.

John Viega wrote: Additionally, with respect to counter mode, it might be best to implement external to the EVP proper interface, just like HMAC. There are a few issues I see that make counter mode a bit different from other modes: 1) You should be able to insert your own function for

[PATCH] argument passing to app_verify_callback

Alas, I meant to send this in weeks ago, before it was too late for 0.9.7; also apologies if this comes as a duplicate (we're changing email addresses here, this can cause obvious chicken-related problems with subscribers-post-only lists...). This is a patch to actually hand the user-supplied

Re: EVP macros for AES

From: Stephen Sprunk [EMAIL PROTECTED] stephen The current state is EAY legacy. His idea was that one should be able stephen to pick out any of the algorithm directories and create a separate stephen library for them (the old libdes is actually exactly the same as stephen crypto/des/).