FW: [openssl.org #2563] PATCH: Improve PRNG seed algorithm for VOS

This ticket can be closed. Dr. Steve Henson applied these changes as check-ins #21861 (head), #21862 (OpenSSL_1_0_1-stable) and #21863 (OpenSSL_1_0_0-stable) on December 19, 2011. Please accept my sincere thanks for applying these changes. PG

[openssl.org #2263] Stale reference to CRYPTO_set_id_callback in doc files; openssl 1.0.0

Openssl 1.0.0 appears to have a stale reference to the deprecated function CRYPTO_set_id_callback in doc/crypto/err.pod (in the SEE ALSO section) and an accurate (AFAICT) reference to it in threads.pod. This function is no longer documented (the info was in threads.pod), so I think the reference

[openssl.org #2157] Typo in 1.0.0-beta5 doc/crypto/X509_STORE_set_verify_cb_func.pod

Line 25 is: =head 1 NOTES but it should read: =head1 NOTES I found this by building openssl-1.0.0-beta5 on a Stratus OpenVOS system and running gmake install_docs and examining the output. According to CVS, the bug was introduced in HEAD with modification #18728 on

RE: [openssl.org #2107] [PATCH] (HEAD and 1.0.0) fix cms-test.pl for Stratus VOS

-Original Message- From: Andy Polyakov via RT [mailto:r...@openssl.org] Sent: Monday, November 23, 2009 3:29 PM To: Green, Paul Cc: openssl-dev@openssl.org Subject: Re: [openssl.org #2107] [PATCH] (HEAD and 1.0.0) fix cms-test.pl for Stratus VOS [...] There is EXE_EXT variable

RE: [openssl.org #1822] Issues w/ fips Makefile

Stephen Henson via RT wrote: [philipp_s...@redfish-solutions.com wrote: The target: fips_standalone_sha1$(EXE_EXT): sha/fips_standalone_sha1.c $(CC) $(CFLAGS) -DFIPSCANISTER_O -o $@ sha/fips_standalone_sha1.c $(FIPSLIBDIR)fipscanister.o is built, but the extension is

RE: [openssl.org #1976] [PATCH 14/14] Cleanup some compile time warnings/magic numbers.

David McCullough proposed the following patch to crypto/engine/eng_cryptodev.c: (extracted from a larger change set): @@ -428,7 +428,7 @@ cryptodev_init_key(EVP_CIPHER_CTX *ctx, const unsigned char *key, if ((state-d_fd = get_dev_crypto()) 0) return (0); -

RE: [openssl.org #1924] Resolved: [patch] Fix refs to _POSIX_C_SOURCE

Thanks for applying this patch, as well as others, on my behalf. PG __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List

[openssl.org #1665] Contribution of aes.pod

I wrote and submitted a documentation file for the OpenSSL AES routines a 13 months ago. I was studying the code and thought I could be helpful to the project. I believe that the file I wrote was entirely accurate at the time of the submission. However, no one has taken the ticket or commented

[openssl.org #1924] [patch] Fix refs to _POSIX_C_SOURCE

diff -ur openssl-1.0.0-beta2/apps/apps.c openssl/apps/apps.c --- openssl-1.0.0-beta2/apps/apps.c 2009-04-03 13:06:35.0 -0400 +++ openssl/apps/apps.c 2009-05-08 13:06:39.0 -0400 @@ -109,10 +109,12 @@ * */ +#ifndef _POSIX_C_SOURCE #define _POSIX_C_SOURCE 2 /* On VMS,

[openssl.org #1925] [patch] Update Configure to support VOS extended names

--- openssl-1.0.0-beta2/Configure 2009-04-06 10:31:34.0 -0400 +++ openssl/Configure 2009-05-08 16:40:06.0 -0400 @@ -191,8 +191,8 @@ cc, cc:-O::(unknown)::, VOS Configurations -vos-gcc,gcc:-O3 -Wall -D_POSIX_C_SOURCE=200112L -D_BSD

[openssl.org #1890] Patch for OpenSSL 1.0.0-beta1 to fix --with-zlib-include and --with-zlib-lib and init the PRNG on VOS.

The standard Stratus VOS build (vos-gcc in Configure) uses the --with-zlib-lib and --with-zlib-include control arguments to Configure. We link openssl with a static copy of zlib which we have just built a few seconds earlier. Sadly, the existing build process does not pass the ZLIB_INCLUDE

[openssl.org #1665] Contribution of aes.pod

I had some time today, so I created aes.pod. I make no claim to any particular expertise in OpenSSL; I simply know how to read C code. Please use this file however you see fit. I encourage folks who are experts in OpenSSL to review it for accuracy. A couple of comments: 1. I took the liberty

RE: [openssl.org #908] Ticket Resolved

Stephen Henson via RT [mailto:[EMAIL PROTECTED] wrote: According to our records, your request has been resolved. Thank you, Stephen! PG __ OpenSSL Project http://www.openssl.org Development

[openssl.org #908] Non-POSIX header in openssl/crypto/x509v3/pcy_node.c

The file openssl/crypto/x509v3/pcy_node.c references the non-POSIX header memory.h. However, if one simply removes this reference, the program still compiles, at least on my system. My feeling is that the line can simply be deleted. But if this causes problems, then it should just be replaced

RE: [openssl.org #499] [PATCH] VOS OpenSSL port

Richard Levitte via RT [mailto:[EMAIL PROTECTED] wrote: Paul, I finally decided to apply the changes, both to the 0.9.7-stable and 0.9.8-dev branches. Please try tomorrow's snapshot to verify that I didn't miss anything. I downloaded openssl-SNAP-20040629.tar.gz and both manually inspected

[openssl.org #499] Patches to OpenSSL for Stratus VOS

The patches described in request-tracker entry #499 are now obsolete. As far as I am concerned, request #499 can be closed. Please see the email thread starting at http://marc.theaimsgroup.com/?l=openssl-devm=108008359106412w=2 for the updated patch. This is a letter I originally sent to

RE: [openssl.org #499] Patches to OpenSSL for Stratus VOS

The following patch should replace the patch originally submitted for request #499. This patch helps OpenSSL build on the Stratus VOS operating system using our POSIX environment. These changes should not affect any other operating system. This patch is nearly identical to the one I mailed to

[openssl.org #499] [PATCH] VOS OpenSSL port

Dear OpenSSL Development Team, This purpose of this letter is to document the patches that Stratus Technologies made to OpenSSL version 0.9.6g to port it to the Stratus VOS operating system and to ask your permission to call the resulting product VOS OpenSSL. This is the first time that we have