An alternative would be to statically link libssl and libcrypto. No
more dependencies.
Pauli
On 20/11/21 3:48 pm, Viktor Dukhovni wrote:
On Sat, Nov 20, 2021 at 01:38:39PM +1100, Grahame Grieve wrote:
I agree it's sure not a core openSSL issue. But surely lots of people
want to use openSSL
您好，您的邮件我已收到，我会尽快阅读，谢谢！
On Sat, Nov 20, 2021 at 01:38:39PM +1100, Grahame Grieve wrote:
> I agree it's sure not a core openSSL issue. But surely lots of people
> want to use openSSL in cross platform apps and openSSL is interested
> in adoption issues?
Most of the users here are building applications that are not notari
>
> > And the rule for that is that all code your application uses must be
> > signed either by you or by apple. I can include both openSSL dylibs in
> > my .app package, and sign all that, but the way libssl loads libcrypto
> > seems to not meet those rules - which specifically exclude symlinking
>
>
> The problem is that symlinking doesn't work in this case. Sure, I can
> install openSSL, and then it works. For me. But I'm trying to distribute an
> application, and to do that on modern macs, I need a hardened run time. And
> the rule for that is that all code your application uses must be
On Sat, Nov 20, 2021 at 06:14:30AM +1100, Grahame Grieve wrote:
> And the rule for that is that all code your application uses must be
> signed either by you or by apple. I can include both openSSL dylibs in
> my .app package, and sign all that, but the way libssl loads libcrypto
> seems to not me
Dear SSL,
Your encryption kit is fantastic. I have been using it to build self-signed
web certificates
and email certificates. I have also been using it to encrypt and decrypt
messages,
all via RSA, ad aes-256. I am running OpenSSL using 64 bit Windows 10, which
is different
to Linux, a litt
The problem is that symlinking doesn't work in this case. Sure, I can install
openSSL, and then it works. For me. But I'm trying to distribute an
application, and to do that on modern macs, I need a hardened run time. And the
rule for that is that all code your application uses must be signed ei
The problem is that symlinking doesn't work in this case. Sure, I can
install openSSL, and then it works. For me. But I'm trying to distribute an
application, and to do that on modern macs, I need a hardened run time. And
the rule for that is that all code your application uses must be signed
eithe
Here's how Macports did it:
1. Installed OpenSSL-1.1.1 into /opt/local/libexec/openssl11;
2. Installed OpenSSL-3.0.0 into /opt/local/libexec/openssl3;
3. Symlinked OpenSSL-3.0.0 libraries into /opt/local/lib (primary directory
where stuff lives);
I added symlinking /opt/local/libexec/openssl11/l
On Fri, Nov 19, 2021 at 05:36:24PM +1100, Grahame Grieve wrote:
> It's very definitely something active that OSX is doing. Here's an OSX
> error generated:
>
> System Integrity Protection: enabled
>
> Crashed Thread:0 Dispatch queue: com.apple.main-thread
>
> Exception Type:EXC
I don't use Brew. I've installed OpenSSL-1.1.1 (and 3.0.0) via Macports, and
have no problem linking and running apps against 1.1.1.
--
Regards,
Uri
There are two ways to design a system. One is to make is so simple there are
obviously no deficiencies.
The other is to make it so complex there
On Friday, 19 November 2021 07:36:24 CET, Grahame Grieve wrote:
It's very definitely something active that OSX is doing. Here's
an OSX error generated:
System Integrity Protection: enabled
Crashed Thread:0 Dispatch queue: com.apple.main-thread
Exception Type:EXC_CRASH (SIGABR
There was a reorg of some of how some of the website works recently...I
guess it broke something.
Matt
On 18/11/2021 23:16, Dr. Matthias St. Pierre wrote:
More strangeness: the side bar for the master and 1.1.1 manpage displays the text
"[an error occurred while processing this directive]"
14 matches
Mail list logo
