Hi,
I'm trying to get OpenSSL 1.0.2u with the FIPS Object Module
2.0.16 in Windows 10 to prompt the user for a smart card's PIN number
every time the application is launched. However, I cannot seem to get it
to work. My UI_METHOD callback functions are not being invoked.
I'm using the
On 1/25/21 6:56 AM, The Doctor wrote:
Anyone using BSD running into basename issues?
I have not, but my use of 3.0 has been limited to KTLS testing
with nginx. Are you referring to whether or not the string
returned by basename(3) is part of the input string or whether
it is a copy stored in
Anyone using BSD running into basename issues?
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
Born
On 23/01/2021 15:22, John Thoe wrote:
> Hi list,
>
> The session reuse question posted on the mailing list earlier
> (https://mta.openssl.org/pipermail/openssl-users/2021-January/013360.html)
> reminded of a somewhat similar question I have.
>
> As per the docs,
>
Hi,
Many of the PKCS12 APIs (ie: PKCS12_create, PKCS12_parse, PKCS12_verify_mac) do
not work in OpenSSL 3.0 when using the fips provider. It looks like that is
because they try to load PKCS12KDF which is not implemented in the fips
provider. These were all working in 1.0.2 with the fips 2.0
On 1/25/21, 10:13, "openssl-users on behalf of The Doctor"
wrote:
Anyone using BSD running into basename issues?
Basename issues on MacOS. Presumably the same as you're having on BSD.
smime.p7s
Description: S/MIME cryptographic signature
