Thank you. I resolved the issue. The root cause was an incorrect cast on the
type when crossing the FFI's boundary.
~slg
‐‐‐ Original Message ‐‐‐
On Tuesday, September 15, 2020 6:06 PM, Matt Caswell wrote:
>
>
> On 15/09/2020 22:48, Sage Gerard wrote:
>
> > I have a Racket program tha
On 15/09/2020 22:48, Sage Gerard wrote:
> I have a Racket program that uses libcrypto through FFI bindings to
> compute digests. It's wrong because it returns different answers than
> `openssl dgst`,regardless of hash algorithm.
>
> The code is here:
> https://github.com/zyrolasting/xiden/blob/
I have a Racket program that uses libcrypto through FFI bindings to compute
digests. It's wrong because it returns different answers than `openssl dgst`,
regardless of hash algorithm.
The code is here:
https://github.com/zyrolasting/xiden/blob/libcrypto/openssl.rkt#L76
It is based on the exampl
Hello everyone. I have the digest of a data (message digest). How I can create
cms signed data using the digest instead of a data? Thanks.
Hi
The openssl version is 1.0.2
Thanks and Regards
Darshan
From: Mody, Darshan Arvindkumar (Darshan)
Sent: Wednesday, 19 June, 19:49
Subject: unknown message digest algorithm
To: 'openssl-users@openssl.org', openssl-...@openssl.org
Cc: Mahajan, Hrishikesh Ulhas (Hrishikesh), Phad
Hi
We are facing issues with regards to SSL_Read operation.
We see the error "error:0D0C50A1:asn1 encoding routines:ASN1_item_verify:
unknown message digest algorithm" during SSL read operation. Below are my
queries
1. Is it possible to have such error during 'read operat
02:03
To: openssl-users@openssl.org
Subject: Re: Unknown message digest algorithm sha256RSA OpenSSL 1.0.1e
On 27-02-2013 23:54, John Unsworth wrote:
> I have a Windows CA that has created a sha256RSA CA cert and server cert.
> However OpenSSL fails to validate them.
>
> C:\MetaAndDi
/CN=macc-JOHN-WIN2K8R2-1-CA
error 7 at 1 depth lookup:certificate signature failure
7892:error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message
digest algorithm:.\crypto\asn1\a_verify.c:141:
C:\MetaAndDirectory\certs>openssl ciphers
DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:E
pth lookup:certificate signature failure
7892:error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message
digest algorithm:.\crypto\asn1\a_verify.c:141:
C:\MetaAndDirectory\certs>openssl ciphers
DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:EDH-RSA-DES-CBC3-SHA:EDH-DS
S-DE
S-CBC3-SHA:DE
Please can you advise is it possible to view a Hash / Message Digest?
Many thanks
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
On Tue, Dec 7, 2010 at 01:50, Dr. Stephen Henson wrote:
> On Tue, Dec 07, 2010, Maxim Kammerer wrote:
>> > The command-line argument "-md" to "openssl cms -sign_receipt" is
>> > apparently ignored, and the default digest algorithm (SHA-1 in my
>> > tests) is used instead.
>
> At present this is a
On Tue, Dec 7, 2010 at 01:50, Dr. Stephen Henson wrote:
> On Tue, Dec 07, 2010, Maxim Kammerer wrote:
>> > The command-line argument "-md" to "openssl cms -sign_receipt" is
>> > apparently ignored, and the default digest algorithm (SHA-1 in my
>> > tests) is used instead.
>
> At present this is a
:asn1 encoding routines:ASN1_item_verify:unknown message
digest algorithm'
if i call OpenSSL_add_all_algorithms() a second time in the startup
sequence of the second thread, the error disappears.
is this a desired behavior? in other applications i have no problems
with multiple threads, this is the
:asn1 encoding routines:ASN1_item_verify:unknown message
digest algorithm'
if i call OpenSSL_add_all_algorithms() a second time in the startup
sequence of the second thread, the error disappears.
is this a desired behavior? in other applications i have no problems
with multiple threads, this is the
argument has the
> > same effect as "-nosmimecap", apparently leaving some unnecessary
> > attributes (like signing time) - contrary to the manual.
>
> Maybe it wasn't clear from my post, but this issue is a bug, not a
> missing feature. The CMS structure for -sign_receip
parently leaving some unnecessary
> attributes (like signing time) - contrary to the manual.
Maybe it wasn't clear from my post, but this issue is a bug, not a
missing feature. The CMS structure for -sign_receipt is very similar
to one for -sign, and both have a field for the selected messa
I am implementing a two-party messages exchange system based on CMS
for Liberté Linux (http://dee.su/liberte).
The command-line argument "-md" to "openssl cms -sign_receipt" is
apparently ignored, and the default digest algorithm (SHA-1 in my
tests) is used instead. In addition, the "-noattr" argu
Kedar Sabnis wrote:
in some specific case SHA1 digest is coming as 152 bits long instead of
160 bits long.
All possible 160 bits values have the same chance of being the output of
a SHA1 digest, *including* those that comprise long strings of all zeros
or all ones.
This mean that, statistic
On Sat, Sep 25, 2010 at 21:09, Kedar Sabnis wrote:
>
> HI,
>
> I am an openSSL User. We implemented SHA1 algorithm.
>
> Here in some specific case SHA1 digest is coming as 152 bits long instead
> of 160 bits long.
>
> Please suggest if any bug fix is there for this issue.
>
> Thanking you in anti
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
Would you perhaps like to explain how you implemented it (i.e., did
you include OpenSSL in your own application, or are you trying to use
it via a script?)? 152 bits is 8 bits -- one byte -- less than 160
bits. Are you using a library or framework that overwrites the last
byte of the buffer with
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
hRSAEncryption
>9d:c6:ef:97:97:4f:ae:23:4c:a2:46:12:83:aa:0a:c8:b9:4a:
>...
>38:42:35:1f:63:69:0b:ed:08:01:56:a7:14:aa:3f:5f
>
> May it help ?
> Raphael
>
> -Message d'origine-
> De : Henrik Nordstrom [mailto:hen...@henriknordstrom.net]
>
iknordstrom.net]
Envoyé : dimanche 14 décembre 2008 00:23
À : Raphael
Cc : squid-us...@squid-cache.org
Objet : Re: [squid-users] TR: [Bulk] Re: [squid-users] Certificate
Validation problem due to Sha 256 message digest
On Fri, 2008-12-12 at 14:53 +0100, Raphael wrote:
> I use Openssl 0.9.8i whic
ssl_algorithms() previously and that did not help
anything. If I called SSLeay_add_all_algorithms(), it bombed out. I think
there's a reported problem calling that method.
Appreciate the help very much.
--
View this message in context:
http://www.nabble.com/Problem-%22unknown-message
pbirk wrote:
I'm trying to use IO-Socket-SSL-1.13_5, Net-SSLeay 1.32 and OpenSSL 0.9.7j.
I have the Perl module coded the following way.
Try connecting with
openssl s_client -state -debug -connect hostname:port and see what details
are returned in the server certificate - that will at
;m using on the client (it's
split up into CA.pem, Cert.pem, and Key.pem).I've seen a similar error
on Google where the resolution was to call SSLeay_add_ssl_algorithms().. I
did this in my application and still have the "unknown message digest
algorithm" error. Does anyon
On Tue, Feb 27, 2007, Zhuang Yuyao wrote:
> Victor Duchovni wrote:
> >On Tue, Feb 27, 2007 at 09:52:38AM +0800, Zhuang Yuyao wrote:
> >
> >>I need to verify a message digest and its signature with a X.509
> >>certificate. As far as I known, the procedur
Victor Duchovni wrote:
On Tue, Feb 27, 2007 at 09:52:38AM +0800, Zhuang Yuyao wrote:
I need to verify a message digest and its signature with a X.509
certificate. As far as I known, the procedure may looks like this:
pubkey = X509_get_pubkey(x);
rsa = EVP_PKEY_get1_RSA(pkey
On Tue, Feb 27, 2007 at 09:52:38AM +0800, Zhuang Yuyao wrote:
> I need to verify a message digest and its signature with a X.509
> certificate. As far as I known, the procedure may looks like this:
> pubkey = X509_get_pubkey(x);
> rsa = EVP_PKEY_get1_RSA(pkey);
> RSA_public_decryp
Hi,
I need to verify a message digest and its signature with a X.509
certificate. As far as I known, the procedure may looks like this:
pubkey = X509_get_pubkey(x);
rsa = EVP_PKEY_get1_RSA(pkey);
RSA_public_decrypt(signature_len, signature, rsa_out, rsa, pad);
memcmp(rsa_out, message_digest
All,
Is there a way to simply extract the message digest from a PKCS #7
signature? Here is a little back ground to hopefully explain the
context.
We have separate data and signature. In order to reduce memory
requirements, we'd like to generate our digest while we decompress the
Hi,
I am new to openssl. I want to know what's a difference between
standard/message-digest/cipher commands. What purpose and when & where
it is used.
Please suggest any url to learn about commands and when ,where & how it
is used.
Thanks,
gmail is the solution. I am on several mailing lists and find no problems with gmail's storage plus threaded UI, super fast message search.WeidongOn 6/23/06,
Torsha Banerjee <[EMAIL PROTECTED]> wrote:
Hello,Can anyone please please tell me how to received the messages from thegroup as digest inste
Torsha Banerjee wrote:
Can anyone please please tell me how to received the messages from the
group as digest instead of individual mails. My mailbox is getting
bombarded with these mails.
Go back to where you signed up ?
Maybe that was at http://www.openssl.org/support/
I'm not sure if Majo
Hello,
Can anyone please please tell me how to received the messages from the
group as digest instead of individual mails. My mailbox is getting
bombarded with these mails.
Thanks,
Torsha
Darryl Miles wrote:
SSL_peek() there isn't much documentation about this one.
My situation is this:
Thank you!
That was exactly it. In in Java the string "SHA" refers to "SHA1". In
OpenSSL "SHA" refers to "SHA0".
Eric
On Oct 1, 2004, at 3:50 PM, David Schwartz wrote:
When I attempt to get a SHA message digest value for a specific string
using Java and
> When I attempt to get a SHA message digest value for a specific string
> using Java and Openssl, I get a different value. I was hoping that I
> could use Openssl to validate the Java result, but have not gotten them
> to agree. It does work for md5...
>
> Here is an example.
When I attempt to get a SHA message digest value for a specific string
using Java and Openssl, I get a different value. I was hoping that I
could use Openssl to validate the Java result, but have not gotten them
to agree. It does work for md5...
Here is an example.
For the sample string
Data Security, Inc./OU=Secure Server Certification Authority
> error 7 at 1 depth lookup:certificate signature failure
> 5904:error:0D07908D:asn1 encoding routines:ASN1_verify:unknown message
> digest algorithm:a_verify.c:86:
>
> I've checked the list, searched the web and re
re failure
5904:error:0D07908D:asn1 encoding routines:ASN1_verify:unknown message
digest algorithm:a_verify.c:86:
I've checked the list, searched the web and read the docs and I
have not been able to resolve the problem so far. I saw that Colin posted
to the list a similar problem back in
On Wed, Feb 23, 2000 at 03:13:28PM +0200, Elen Mägioja wrote:
> The code i managed to write is added below. It seems to work
> ok... no errors... the signature gets printed out... but what makes
> me wonder is the output format of the signature. That's not in the
> format I want to get... Shouldn
Hi,
I have a message digest i want to sign with my RSA private key and i just want the
signature printed out on screen. I found a lot of
help in demos/sign.c but I still have problems.
The code i managed to write is added below. It seems to work ok... no errors... the
signature gets printed
44 matches
Mail list logo