Re: Custom Build Errors
Neil Horman <[email protected]> Thu, 30 Apr 2026 09:53:19 -0400
| Newsgroups | gmane.comp.encryption.openssl.user |
|---|---|
| Message-ID | <CAJbOq14pRj-7hnSSYrabXgovrqTbqGWrM_jfPjjvu9JpPo+ZRA@mail.gmail.com> |
--00000000000038aa880650adca8b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Adding the '/' makes sense, as I expect that PKI/openssl-3.6.0 isn't in
your path
As for the linker errors, I'm fairly certain you've somehow mistakenly
copied the libcrypto.so.3 library from your 3.1.2 build
into /PKI/openssl-3.6.0/lib
If you run this command:
objdump -x /PKI/openssl-3.6.0/apps/openssl
you'll see output that includes this table:
Version References:
required from libc.so.6:
0x069691b3 0x00 16 GLIBC_2.33
0x06969194 0x00 15 GLIBC_2.14
0x069691b4 0x00 13 GLIBC_2.34
0x069691b8 0x00 11 GLIBC_2.38
0x0d696913 0x00 09 GLIBC_2.3
0x09691a75 0x00 06 GLIBC_2.2.5
required from libssl.so.3:
0x06702f20 0x00 18 OPENSSL_3.4.0
0x06702d20 0x00 05 OPENSSL_3.2.0
0x06702b20 0x00 03 OPENSSL_3.0.0
required from libcrypto.so.3:
0x06702b29 0x00 17 OPENSSL_3.0.9
0x06702b23 0x00 14 OPENSSL_3.0.3
0x06702e20 0x00 12 OPENSSL_3.3.0
0x06703020 0x00 10 OPENSSL_3.5.0
0x06702120 0x00 08 OPENSSL_3.6.0
0x06702f20 0x00 07 OPENSSL_3.4.0
0x06702d20 0x00 04 OPENSSL_3.2.0
0x06702b20 0x00 02 OPENSSL_3.0.0
That says the ELF file that is your openssl app requires that symbols from
the OPENSSL_3.0.0 through OPENSSL_3.6.0 need to be resolved by this binary
in libcrypto.so.3, as well as version 3.0.0, 3.2.0 and 3.4.0 from
libssl.so.3. This makes sense, because as we add api calls in minor
versions the build system tags them with the version number in which they
are added.
If you now run this command:
objdump -x /PKI/openssl-3.6.0/lib/libcrypto.so.3
What you _should_ see is a table that looks like this:
Version definitions:
1 0x01 0x06af4743 libcrypto.so.3
2 0x00 0x06702b20 OPENSSL_3.0.0
3 0x00 0x06702b23 OPENSSL_3.0.3
OPENSSL_3.0.0
4 0x00 0x06702b28 OPENSSL_3.0.8
OPENSSL_3.0.3
5 0x00 0x06702b29 OPENSSL_3.0.9
OPENSSL_3.0.8
6 0x00 0x06702c20 OPENSSL_3.1.0
OPENSSL_3.0.9
7 0x00 0x06702d20 OPENSSL_3.2.0
OPENSSL_3.1.0
8 0x00 0x06702e20 OPENSSL_3.3.0
OPENSSL_3.2.0
9 0x00 0x06702f20 OPENSSL_3.4.0
OPENSSL_3.3.0
10 0x00 0x06703020 OPENSSL_3.5.0
OPENSSL_3.4.0
11 0x00 0x06702120 OPENSSL_3.6.0
OPENSSL_3.5.0
Which define the versions that the openssl app needs from the library, and
everything matches up.
What I expect you _will_ see however is a table that looks like this:
objdump -x /PKI/openssl-3.6.0/lib/libcrypto.so.3
Version definitions:
1 0x01 0x06af4743 libcrypto.so.3
2 0x00 0x06702b20 OPENSSL_3.0.0
i.e. the library being pointed to by LD_LIBRARY_PATH doesn't contain the
version definitions that the application requires.
I should be a bit more through here. I asserted that somehow you
inadvertently copied libcrypto.so.3 and libssl.so.3 from a non-matching
build to /PKI/openssl-3.6.0/lib/ . Its possible that didn't happen.
Instead it may also be possible that the needed libraries in
/PKI/openssl-3.6.0/lib/ don't exist there at all. If that were the case,
the LD_LIBRARY_PATH lookup would fail and the runtime loader would fall
back to the standard search path, loading /usr/lib64/libcrypto.so.3, which
on ubuntu 22.04 would be a build from openssl-3.0.2, which would give you
exactly the same error.
I would suggest the following:
1) confirm that /PKI/openssl-3.6.0/lib/libcrypto.so.3 and
/PKI/openssl-3.6.0/lib/libssl.so.3 exist
2) Assuming that they do, run the above objdump commands to confirm the
output I presented.
If the result of (1) is that those files don't exist in that location, the
problem is that you're loading the system libcrypto/libssl and we need to
adjust either your library locations or search path to find the right
version that you want to use.
If the result of (1) is that those files do exist there in that location,
then my initial theory is correct, and you've got an old version of
libcrypto/libssl where it shouldn't be.
Regards
Neil
On Thu, Apr 30, 2026 at 9:11=E2=80=AFAM Mark Sigsbee <[email protected]> w=
rote:
> When I enter this: LD_LIBRARY_PATH=3D/PKI/openssl-3.6.0/lib
> PKI/openssl-3.6.0/apps/openssl list -providers -verbose
>
> I get "command not found".
>
> When I enter this: LD_LIBRARY_PATH=3D/PKI/openssl-3.6.0/lib
> /PKI/openssl-3.6.0/apps/openssl list -providers -verbose #added forward
> slash in front of second PKI
>
> I get the crazy response that I shared above.
>
> Thanks,
>
> Mark
>
>
> On Wed, Apr 15, 2026 at 9:31=E2=80=AFAM Neil Horman <[email protected]>=
wrote:
>
>> you don't have the library search path configured correctly on your
>> platform. Try running:
>>
>> LD_LIBRARY_PATH=3D/PKI/openssl-3.6.0/lib PKI/openssl-3.6.0/apps/openssl
>> list -providers -verbose
>>
>> That will allow the application to run. You may also need to set
>> OPENSSL_CONF and OPENSSL_MODULES appropriately to find the needed
>> configuration and provider DSO's
>>
>> To avoid needing to set these values you need to configure openssl using
>> the --prefix option to set the latter two variables automatically. To
>> avoid the need for LD_LIBRARY_PATH, you either need to configure your
>> environment to add /PKI/openssl-3.6.0/lib[64] to the library search path
>> globally, or install the library to a location already in the search pat=
h
>> (though the latter isn't recommended if you are using a system with a
>> default openssl already configured there).
>>
>> Neil
>>
>>
>> On Wed, Apr 15, 2026 at 9:13=E2=80=AFAM Mark Sigsbee <[email protected]=
> wrote:
>>
>>> I'm trying to build 3.6.0 with 3.2.1 for its approved FIPS library on
>>> Ubuntu 22.04. I know the default version of OpenSSL is 3.0 and basicall=
y
>>> leave it alone or the world will come to an end.
>>>
>>> I'm building a newer version hoping to resolve issues that I'm getting
>>> with 3.0 and confirmed by Ubuntu Pro support.
>>>
>>> I d/l'ed both into $ /PKI.
>>> I followed the build instructions provided here: openssl/README-FIPS.m=
d
>>> at master =C2=B7 openssl/openssl
>>> <https://github.com/openssl/openssl/blob/master/README-FIPS.md>
>>>
>>> My check agrees with the check results in the readme.
>>>
>>> When I execute:
>>> $ sudo /PKI/openssl-3.6.0/apps/openssl list -providers -verbose
>>>
>>> I get this:
>>> /PKI$ sudo /PKI/openssl-3.6.0/apps/openssl list -providers -verbose
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libssl.so.3:
>>> version `OPENSSL_3.4.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libssl.so.3:
>>> version `OPENSSL_3.2.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.0.9' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.3.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.5.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.6.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.4.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>> /PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3:
>>> version `OPENSSL_3.2.0' not found (required by
>>> /PKI/openssl-3.6.0/apps/openssl)
>>>
>>> How do I correct this and get my desired result?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "openssl-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
>>> To view this discussion visit
>>> https://groups.google.com/a/openssl.org/d/msgid/openssl-users/CAPqvXLPc=
7dDaR3S05bmdSAaFJSZ0k5uSmCs0AY_juicFindorQ%40mail.gmail.com
>>> <https://groups.google.com/a/openssl.org/d/msgid/openssl-users/CAPqvXLP=
c7dDaR3S05bmdSAaFJSZ0k5uSmCs0AY_juicFindorQ%40mail.gmail.com?utm_medium=3De=
mail&utm_source=3Dfooter>
>>> .
>>>
>>
--=20
You received this message because you are subscribed to the Google Groups "=
openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msg=
id/openssl-users/CAJbOq14pRj-7hnSSYrabXgovrqTbqGWrM_jfPjjvu9JpPo%2BZRA%40ma=
il.gmail.com.
--00000000000038aa880650adca8b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Adding the '/' makes sense, as I expect that PKI/o=
penssl-3.6.0 isn't in your path<div><br></div><div>As for the linker er=
rors, I'm fairly certain you've somehow mistakenly copied the libcr=
ypto.so.3 library from your 3.1.2 build into=C2=A0/PKI/openssl-3.6.0/lib</d=
iv><div><br></div><div>If you run this command:</div><div>objdump -x=C2=A0/=
PKI/openssl-3.6.0/apps/openssl</div><div><br></div><div>you'll see outp=
ut that includes this table:</div><div>Version References:<br>=C2=A0 requir=
ed from libc.so.6:<br>=C2=A0 =C2=A0 0x069691b3 0x00 16 GLIBC_2.33<br>=C2=A0=
=C2=A0 0x06969194 0x00 15 GLIBC_2.14<br>=C2=A0 =C2=A0 0x069691b4 0x00 13 G=
LIBC_2.34<br>=C2=A0 =C2=A0 0x069691b8 0x00 11 GLIBC_2.38<br>=C2=A0 =C2=A0 0=
x0d696913 0x00 09 GLIBC_2.3<br>=C2=A0 =C2=A0 0x09691a75 0x00 06 GLIBC_2.2.5=
<br>=C2=A0 required from libssl.so.3:<br>=C2=A0 =C2=A0 0x06702f20 0x00 18 O=
PENSSL_3.4.0<br>=C2=A0 =C2=A0 0x06702d20 0x00 05 OPENSSL_3.2.0<br>=C2=A0 =
=C2=A0 0x06702b20 0x00 03 OPENSSL_3.0.0<br>=C2=A0 required from libcrypto.s=
o.3:<br>=C2=A0 =C2=A0 0x06702b29 0x00 17 OPENSSL_3.0.9<br>=C2=A0 =C2=A0 0x0=
6702b23 0x00 14 OPENSSL_3.0.3<br>=C2=A0 =C2=A0 0x06702e20 0x00 12 OPENSSL_3=
.3.0<br>=C2=A0 =C2=A0 0x06703020 0x00 10 OPENSSL_3.5.0<br>=C2=A0 =C2=A0 0x0=
6702120 0x00 08 OPENSSL_3.6.0<br>=C2=A0 =C2=A0 0x06702f20 0x00 07 OPENSSL_3=
.4.0<br>=C2=A0 =C2=A0 0x06702d20 0x00 04 OPENSSL_3.2.0<br>=C2=A0 =C2=A0 0x0=
6702b20 0x00 02 OPENSSL_3.0.0<br></div><div><br></div><div>That says the EL=
F file that is your openssl app requires that symbols from the OPENSSL_3.0.=
0 through OPENSSL_3.6.0 need to be resolved by this binary in libcrypto.so.=
3, as well as version 3.0.0, 3.2.0 and 3.4.0 from libssl.so.3.=C2=A0 This m=
akes sense, because as we add api calls in minor versions the build system =
tags them with the version number in which they are added.</div><div><br></=
div><div>If you now run this command:</div><div>objdump -x=C2=A0/PKI/openss=
l-3.6.0/lib/libcrypto.so.3</div><div><br></div><div>What you _should_ see i=
s a table that looks like this:</div><div>Version definitions:<br>1 0x01 0x=
06af4743 libcrypto.so.3<br>2 0x00 0x06702b20 OPENSSL_3.0.0<br>3 0x00 0x0670=
2b23 OPENSSL_3.0.3<br> OPENSSL_3.0.0 <br>4 0x00 0x06702b28 OPENSSL_3.0.8<br=
> OPENSSL_3.0.3 <br>5 0x00 0x06702b29 OPENSSL_3.0.9<br> OPENSSL_3.0.8 <br>6=
0x00 0x06702c20 OPENSSL_3.1.0<br> OPENSSL_3.0.9 <br>7 0x00 0x06702d20 OPEN=
SSL_3.2.0<br> OPENSSL_3.1.0 <br>8 0x00 0x06702e20 OPENSSL_3.3.0<br> OPENSSL=
_3.2.0 <br>9 0x00 0x06702f20 OPENSSL_3.4.0<br> OPENSSL_3.3.0 <br>10 0x00 0x=
06703020 OPENSSL_3.5.0<br> OPENSSL_3.4.0 <br>11 0x00 0x06702120 OPENSSL_3.6=
.0<br> OPENSSL_3.5.0</div><div><br></div><div>Which define the versions tha=
t the openssl app needs from the library, and everything matches up.</div><=
div><br></div><div>What I expect you _will_ see however is a table that loo=
ks like this:</div><div>objdump=C2=A0=C2=A0-x /PKI/openssl-3.6.0/lib/libcry=
pto.so.3<br></div><div>Version definitions:<br>1 0x01 0x06af4743 libcrypto.=
so.3<br>2 0x00 0x06702b20 OPENSSL_3.0.0</div><div><br></div><div>i.e. the l=
ibrary being pointed to by LD_LIBRARY_PATH doesn't contain the version =
definitions that the application requires.</div><div><br></div><div>I shoul=
d be a bit more through here.=C2=A0 I asserted that somehow you inadvertent=
ly copied libcrypto.so.3 and libssl.so.3 from a non-matching build to=C2=A0=
/PKI/openssl-3.6.0/lib/ .=C2=A0 Its possible that didn't happen.=C2=A0 =
Instead it may also be possible that the needed libraries=C2=A0in /PKI/open=
ssl-3.6.0/lib/ don't exist there at all.=C2=A0 If that were the case, t=
he LD_LIBRARY_PATH lookup would fail and the runtime loader would fall back=
to the standard search path, loading /usr/lib64/libcrypto.so.3, which on u=
buntu 22.04 would be a build from openssl-3.0.2, which would give you exact=
ly the same error.</div><div><br></div><div>I would suggest the following:<=
/div><div>1) confirm that /PKI/openssl-3.6.0/lib/libcrypto.so.3 and /PKI/op=
enssl-3.6.0/lib/libssl.so.3 exist</div><div>2) Assuming that they do, run t=
he above objdump commands to confirm the output I presented.</div><div><br>=
</div><div>If the result of (1) is that those files don't exist in that=
location, the problem is that you're loading the system libcrypto/libs=
sl and we need to adjust either your library locations or search path to fi=
nd the right version that you want to use.</div><div><br></div><div>If the =
result of (1) is that those files do exist there in that location, then my =
initial theory is correct, and you've got an old version of libcrypto/l=
ibssl where it shouldn't be.</div><div><br></div><div>Regards</div><div=
>Neil</div><div><br></div><div><br></div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 30, 2026 at 9:11=E2=80=
=AFAM Mark Sigsbee <<a href=3D"mailto:[email protected]" target=3D"_bla=
nk">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr">When I enter this: LD_LIBRARY_PATH=
=3D/PKI/openssl-3.6.0/lib PKI/openssl-3.6.0/apps/openssl list -providers -v=
erbose<div><br>I get "command not found".<br><br>When I enter thi=
s: LD_LIBRARY_PATH=3D/PKI/openssl-3.6.0/lib /PKI/openssl-3.6.0/apps/openssl=
list -providers -verbose #added forward slash in front of second PKI<br><b=
r>I get the crazy response that I shared above.<br><br>Thanks,</div><div><b=
r>Mark</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Wed, Apr 15, 2026 at 9:31=E2=80=AFAM Neil Hor=
man <<a href=3D"mailto:[email protected]" target=3D"_blank">nhorman@op=
enssl.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr">you=C2=A0don't have the library search path=
configured correctly on your platform.=C2=A0 Try running:<div><br></div><d=
iv>LD_LIBRARY_PATH=3D/PKI/openssl-3.6.0/lib PKI/openssl-3.6.0/apps/openssl =
list -providers -verbose</div><div><br></div><div>That will allow the appli=
cation to run.=C2=A0 You may also need to set OPENSSL_CONF and OPENSSL_MODU=
LES appropriately to find the needed configuration and provider DSO's</=
div><div><br></div><div>To avoid needing to set these values you need to co=
nfigure openssl using the --prefix option to set the latter two variables=
=C2=A0automatically.=C2=A0 To avoid the need for LD_LIBRARY_PATH, you eithe=
r need to configure your environment to add /PKI/openssl-3.6.0/lib[64] to t=
he library search path globally, or install the library to a location alrea=
dy in the search path (though the latter isn't recommended if you are u=
sing a system with a default openssl already configured there).</div><div><=
br></div><div>Neil</div><div><br></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 15, 2026 at 9:13=E2=80=
=AFAM Mark Sigsbee <<a href=3D"mailto:[email protected]" target=3D"_bla=
nk">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr">I'm trying to build 3.6.0 with 3=
.2.1 for its approved FIPS library on Ubuntu 22.04. I know the default vers=
ion of OpenSSL is 3.0 and basically leave it alone or the world will come t=
o an end.<br><br>I'm building a newer version hoping to resolve issues =
that I'm getting with 3.0 and confirmed by Ubuntu Pro support.<div><br>=
I d/l'ed both into $ /PKI.<br>I followed the build instructions provide=
d here:=C2=A0
<a href=3D"https://github.com/openssl/openssl/blob/master/README-FIPS.md" t=
arget=3D"_blank">openssl/README-FIPS.md at master =C2=B7 openssl/openssl</a=
><br><br>My check agrees with the check results in the readme.<br><br>When =
I execute:<br>$ sudo /PKI/openssl-3.6.0/apps/openssl list -providers -verbo=
se<br><br>I get this:<br>/PKI$ sudo /PKI/openssl-3.6.0/apps/openssl list -p=
roviders -verbose<br>/PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu=
/libssl.so.3: version `OPENSSL_3.4.0' not found (required by /PKI/opens=
sl-3.6.0/apps/openssl)<br>/PKI/openssl-3.6.0/apps/openssl: /lib/x86_64-linu=
x-gnu/libssl.so.3: version `OPENSSL_3.2.0' not found (required by /PKI/=
openssl-3.6.0/apps/openssl)<br>/PKI/openssl-3.6.0/apps/openssl: /lib/x86_64=
-linux-gnu/libcrypto.so.3: version `OPENSSL_3.0.9' not found (required =
by /PKI/openssl-3.6.0/apps/openssl)<br>/PKI/openssl-3.6.0/apps/openssl: /li=
b/x86_64-linux-gnu/libcrypto.so.3: version `OPENSSL_3.3.0' not found (r=
equired by /PKI/openssl-3.6.0/apps/openssl)<br>/PKI/openssl-3.6.0/apps/open=
ssl: /lib/x86_64-linux-gnu/libcrypto.so.3: version `OPENSSL_3.5.0' not =
found (required by /PKI/openssl-3.6.0/apps/openssl)<br>/PKI/openssl-3.6.0/a=
pps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3: version `OPENSSL_3.6.0&#=
39; not found (required by /PKI/openssl-3.6.0/apps/openssl)<br>/PKI/openssl=
-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3: version `OPENSSL=
_3.4.0' not found (required by /PKI/openssl-3.6.0/apps/openssl)<br>/PKI=
/openssl-3.6.0/apps/openssl: /lib/x86_64-linux-gnu/libcrypto.so.3: version =
`OPENSSL_3.2.0' not found (required by /PKI/openssl-3.6.0/apps/openssl)=
<br><br>How do I correct this and get my desired result?=C2=A0<br><div><br>=
</div></div></div>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;openssl-users" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org" target=3D"=
_blank">openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/a/openss=
l.org/d/msgid/openssl-users/CAPqvXLPc7dDaR3S05bmdSAaFJSZ0k5uSmCs0AY_juicFin=
dorQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter" target=3D=
"_blank">https://groups.google.com/a/openssl.org/d/msgid/openssl-users/CAPq=
vXLPc7dDaR3S05bmdSAaFJSZ0k5uSmCs0AY_juicFindorQ%40mail.gmail.com</a>.<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;openssl-users" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org">openssl-us=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/a/openss=
l.org/d/msgid/openssl-users/CAJbOq14pRj-7hnSSYrabXgovrqTbqGWrM_jfPjjvu9JpPo=
%2BZRA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://gro=
ups.google.com/a/openssl.org/d/msgid/openssl-users/CAJbOq14pRj-7hnSSYrabXgo=
vrqTbqGWrM_jfPjjvu9JpPo%2BZRA%40mail.gmail.com</a>.<br />
--00000000000038aa880650adca8b--