: Chris Outwin
Sent: Monday, December 28, 2020 9:43 PM
To: Dr. Matthias St. Pierre
Subject: Re: SHA256 openssl-1.1.1i Checksum Error
Thank you for your prompt reply. Removing the quotes from VERSION=“1.1.1i”
allowed the script to run.
On Dec 28, 2020, at 12:49 PM, Dr. Matthias St. Pierre
> From: openssl-users On Behalf Of Dr.
> Matthias St. Pierre
> Sent: Monday, 28 December, 2020 11:50
> I have no experience with zsh, but it seems that quoting is handled
> differently by zsh?
Is the problem that quoting is handled differently, or that he actually had
Unicode left-double-quote
I have no experience with zsh, but it seems that quoting is handled differently
by zsh?
At least it looks like the double quotes ended up in the GET line and you
simply received
an HTTP 404 Not Found (which is the reason why your digest isn’t correct.)
HTH,
Matthias
> GET /source/openssl-“1.1.
My problem was that my server certificate was not SHA-256 capable. As
soon as I generated a new server certificate based on an openssl that
supported SHA-256, I was able to communicate with the server.
From: Jerry Blasdel/USA/CSC@CSC
To: openssl-users@openssl.org
Date: 04/03/2014 11
Hi Aya,
I have not tried this with a self-signed certificate, but putting the
"-sha256" option in the signature command has worked for me before, i.e.,
x509 -req -in server.csr -signkey server.key -out server.crt -sha256
The can check the attribute with:
x509 -text -in server.crt
...
Signatur
On Thu, Nov 07, 2013 at 03:51:38PM -0500, Dave Thompson wrote:
> To support the (four original) SHA-2 hashes as such, yes.
> But: if you want to sign (and I think verify?) SHA2 and DSA or ECDSA,
> you need the new signature/hash mechanism in 1.0.0, and if
> you want TLSv1.2 suites using HMAC-SHA
Yes, I need to sign and verify so 1.0.0 or 1.0.1 even better. Thanks so much
for the info.
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dave Thompson
Sent: Thursday, November 07, 2013 3:52 PM
To: openssl-users@openssl.org
Hello,
>
> I understand that openssl-0.9.8 support SHA256.
Is supported as message digest itself.
> I used the latest openssl-0.9.8 (built on linux) and
> executed the following commands.
>
> 1) ./openssl ciphers -v ALL
>
> I dont find any mention of SHA256 at all. Part of the
> output is as fo
On Fri, 2006-11-17 at 16:16 -0800, [EMAIL PROTECTED] wrote:
> Which version of OpenSSL introduced sha256 support? I cannot find it
> in the changelogs on the site...
0.9.8 and above.
Best regards,
--
Marek Marcola <[EMAIL PROTECTED]>
__
Thanks very much Victor ...
I see exactly what you mean. The first character in that hash result being a
'\0' char is masking the rest of the data when it's looked at like a C char
array. Looking at my memory directly I now see the other bytes of data. So it
always did contain the hash value
On Tue, Feb 07, 2006 at 09:34:49PM -0800, FenderQ wrote:
> Using SHA256 in OpenSSL 0.9.8 ...
> Does anyone get no result with data "sp0"?
> Please note: sp0 is lowercase above and without the "'s nor the ? char
>
> I have tried these two OpenSSL versions:
> openssl-0.9.8a.tar.gz
> openssl-0.9.8-s
On Thu, Apr 11, 2002 at 02:01:51AM -0700, Aleksey Sanin wrote:
> AFAIK, the last fix was made back in October and it addressed
> an attack related to random numbers generator. I am not sure
> I have any fresh insider information on the topic :)
> The problem is that SHA256 and greater are became r
AFAIK, the last fix was made back in October and it addressed
an attack related to random numbers generator. I am not sure
I have any fresh insider information on the topic :)
The problem is that SHA256 and greater are became required
in other standards (XML Encryption, for example). And quick
On Wed, Apr 10, 2002 at 11:08:24PM -0700, Aleksey Sanin wrote:
> Just wonder why OpenSSL has no SHA256/512 support
> ("grep -i sha `find . -name "*"` | grep 256" in
> openssl-0.9.7-stable-SNAP-20020319
> returns only bunch of *_AES_256_SHA references)?
> Does there exist any reason or simply nobo
14 matches
Mail list logo
