Hi,
I have created a TLS connection with SSL_connect(ssl) successfully. Then I call
SSL_shutdown(ssl) to close the TLS connectio sussessfully. Thenn I want to do
the reopen with SSL_connect(ssl) . But I found it failed. The return value from
::SSL_get_error (ssl, status) is SSL_ERROR_SYSCALL, a
Would it be a good idea to create an OpenSSL FIPS-mode users' list, to
take issues specifically related to FIPS off of the main users list,
and attract the attention of those who work only with FIPS
validation-required environments? I'm just tossing this idea out
here, because it seems as though
Hi,
As the title says - debugging ike msging I have the encrypted payload. I
need to decrypt. I have this data using ethereal. Can i use the keys
(available via ikeadm dump p1 on Solaris) to decrypt using openssl api.
Have been having problems with that. Any help would be appreciated,
Th
Hi,
As the title says - debugging ike msging I have the encrypted payload.
I need to decrypt. I have this data using ethereal. Can i use the
keys (available via ikeadm dump p1 on Solaris) to decrypt using openssl
api. Have been having problems with that. Any help would be appreciated,
Th
Hi,
I have created a TLS connection with SSL_connect(ssl) successfully. Then I call
SSL_shutdown(ssl) to close the TLS connectio sussessfully. Thenn I want to do
the reopen with SSL_connect(ssl) . But I found it failed. The return value from
::SSL_get_error (ssl, status) is SSL_ERROR_SYSCALL, a
Kyle Hamilton wrote:
> Also, I assume it compiles with 0.9.7, 0.9.8, and 0.9.9?
I presume so, I'm working with 0.9.8b.
Also only tested on Linux. It should be simple to get running on any
unix with pthread support.
> How is it described -- a precompiled byte sequence?
Byte sequence ? Its
I've used a perl script to convert all the .pod documentation
to XML, docbook format.
Each is a chapter, wouldn't take much to build a wrapper
which included them all in a 'book'
Attached is an example. x509_new.pod
in html format, from the xml.
docbook to pdf is also available, thanks to Norm
isn't ssl_test.c a sufficient starting point?
smime.p7s
Description: S/MIME Cryptographic Signature
If it's 4800 lines, it should be trivial to send via email -- just tar
and either gzip or bzip2, and mail it off. (If you would mail the
initial release to me directly, I'd appreciate it -- but I can wait
until it's in the OpenSSL cvs if necessary.)
Also, I assume it compiles with 0.9.7, 0.9.8,
Kyle Hamilton wrote:
2) I want to determine what the boundaries of each function are, and
document them appropriately (and perhaps write up patches to fix any
problems that I find). The OpenSSL documentation has been FAR too
sparse and incomplete since the project's inception (building on
SSLea
I would be most interested in this, for two reasons:
1) I'm on the IETF TLS mailing list, and would like something to make
sure that I don't break regression with my local copy of the openssl
code when I'm doing a test implementation of TLS 1.2 (and its
extension mechanism).
2) I want to determ
Question should have been in openssl-users@
You dont give -passin argument. Leave it out and the
command will automatically take the password from the
command line
--- via RT <[EMAIL PROTECTED]> wrote:
>
> Configuration: Windows XP.
> Open SSL Version: 0.9.8b
>
> The following command:
> open
Configuration: Windows XP.
Open SSL Version: 0.9.8b
The following command:
openssl pkcs12 -in infile.p12 -passin stdin
Outputs this:
Mac verify error: invalid password?
However, if password is passed directly in command line it works fine.
It seems to be a problem dealing with stdin.
_
13 matches
Mail list logo
