Unsubscribe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





> On 3 Feb 2024, at 12:00 PM, openssl-users-request@xxxxxxxxxxx wrote:
> 
> Send openssl-users mailing list submissions to
>    openssl-users@xxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://mta.openssl.org/mailman/listinfo/openssl-users
> or, via email, send a message with subject or body 'help' to
>    openssl-users-request@xxxxxxxxxxx
> 
> You can reach the person managing the list at
>    openssl-users-owner@xxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of openssl-users digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: HTML page broken (it seems) (Gisle Vanem)
>   2. Re: HTML page broken (it seems) (Matt Caswell)
>   3. I do not understand DigestSignInit (Steffen Nurpmeso)
>   4. Re: I do not understand DigestSignInit (Steffen Nurpmeso)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 2 Feb 2024 16:49:02 +0100
> From: Gisle Vanem <gvanem@xxxxxxxx>
> To: openssl-users@xxxxxxxxxxx
> Subject: Re: HTML page broken (it seems)
> Message-ID: <b0d9356a-68ab-663c-d00a-b9f7c43ef7a6@xxxxxxxx>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> Steffen Nurpmeso wrote:
>> Looking at
>> 
>>   https://www.openssl.org/community/mailinglists.html
>> 
>> it seems the page is broken.
> 
> Looks fine to me. What is "broken"?
> 
> --
> --gv
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 2 Feb 2024 15:52:02 +0000
> From: Matt Caswell <matt@xxxxxxxxxxx>
> To: openssl-users@xxxxxxxxxxx
> Subject: Re: HTML page broken (it seems)
> Message-ID: <a1561b10-3903-47ad-af87-2fe30e80204c@xxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> 
> 
>> On 02/02/2024 15:49, Gisle Vanem via openssl-users wrote:
>> Steffen Nurpmeso wrote:
>>> Looking at
>>> 
>>> ?? https://www.openssl.org/community/mailinglists.html
>>> 
>>> it seems the page is broken.
>> 
>> Looks fine to me. What is "broken"?
>> 
> 
> It was broken. It got fixed a few hours ago:
> 
> https://github.com/openssl/web/pull/460
> 
> Matt
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sat, 03 Feb 2024 03:46:16 +0100
> From: Steffen Nurpmeso <steffen@xxxxxxxxxx>
> To: openssl-users@xxxxxxxxxxx
> Subject: I do not understand DigestSignInit
> Message-ID: <20240203024616.Vqb451KI@steffen%sdaoden.eu>
> 
> Hello.
> 
> Has anyone knowledge on how i can automatically determine whether
> i need to call
> 
>  EVP_DigestSignInit(mdcp, NIL, mdp, NIL, pkeyp)
> 
> or
> 
>  EVP_DigestSignInit(mdcp, NIL, NIL, NIL, pkeyp)
> 
> That is, a way to determine whether a EVP_PKEY is "configurable
> regarding the used message-digest", or whether it has a built-in
> approach of digest-signing?
> 
> Any hint to overcome
> 
>  !EVP_DigestSignInit(mdcp, NIL, mdp, NIL, pkeyp) &&
>    !EVP_DigestSignInit(mdcp, NIL, NIL, NIL, pkeyp)
> 
> would be very much appreciated, especially since i cannot truly
> such useful non-textual info out of the error of the first (e,
> GET_LIB,GET_REASON,..):
> 
>  ERROR 478150778 57 122 error:1C80007A:Provider routines::invalid digest
> 
> A nice weekend i wish everyone,
> Ciao,
> 
> --steffen
> |
> |Der Kragenbaer,                The moon bear,
> |der holt sich munter           he cheerfully and one by one
> |einen nach dem anderen runter  wa.ks himself off
> |(By Robert Gernhardt)
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Sat, 03 Feb 2024 04:03:34 +0100
> From: Steffen Nurpmeso <steffen@xxxxxxxxxx>
> To: openssl-users@xxxxxxxxxxx
> Subject: Re: I do not understand DigestSignInit
> Message-ID: <20240203030334.EygrQsRw@steffen%sdaoden.eu>
> 
> Steffen Nurpmeso wrote in
> <20240203024616.Vqb451KI@steffen%sdaoden.eu>:
> |Has anyone knowledge on how i can automatically determine whether
> |i need to call
> |
> |  EVP_DigestSignInit(mdcp, NIL, mdp, NIL, pkeyp)
> |
> |or
> |
> |  EVP_DigestSignInit(mdcp, NIL, NIL, NIL, pkeyp)
> |
> |That is, a way to determine whether a EVP_PKEY is "configurable
> |regarding the used message-digest", or whether it has a built-in
> |approach of digest-signing?
> 
> And also, while i am here, is there any PKEY interface that tells
> me whether the PKEY supports stream-based aka iterative
> Update/Final?  Just in case there is a key type which allows
> "configurable message-digest" but still requires one-shot because
> it iterates over the data multiple times, or so.
> 
> Thank you!!
> 
> --steffen
> |
> |Der Kragenbaer,                The moon bear,
> |der holt sich munter           he cheerfully and one by one
> |einen nach dem anderen runter  wa.ks himself off
> |(By Robert Gernhardt)
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> openssl-users mailing list
> openssl-users@xxxxxxxxxxx
> https://mta.openssl.org/mailman/listinfo/openssl-users
> 
> 
> ------------------------------
> 
> End of openssl-users Digest, Vol 111, Issue 3
> *********************************************




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux