gt; > 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 in cross platform apps and
>
> > 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
- C. A. R. Hoare
>
>
> On 11/19/21, 13:16, "openssl-users on behalf of Viktor Dukhovni" <
> openssl-users-boun...@openssl.org on behalf of openssl-us...@dukhovni.org>
> wrote:
>
> On Fri, Nov 19, 2021 at 05:36:24PM +
at 04:31:26PM +1100, Grahame Grieve wrote:
>
> > I'm trying to get my application that uses openSSL 1.1 running on OSX.
> I've
> > installed them using homebrew, but I can't get past Apple's gates around
> > blocking use of openSSL.
>
> I don't thi
I'm trying to get my application that uses openSSL 1.1 running on OSX. I've
installed them using homebrew, but I can't get past Apple's gates around
blocking use of openSSL. I've copied both dylibs into my app
/Contents/MacOS folder, and signed both of them, and I load them from the
that location,
I am implementing a JWS based specification using openSSL. My code is
below, in pascal. I'm trying to reproduce this test case here:
https://datatracker.ietf.org/doc/html/rfc7515#appendix-A.3.1
I get a different outcome from EVP_DigestSignInit / EVP_DigestUpdate /
EVP_DigestSignFinal from that spe
thanks very much. I will see what I can do about the indy distribution
which seems to have fallen behind
Grahame
On Sat, Jan 19, 2019 at 9:27 AM Matt Caswell wrote:
>
>
> On 18/01/2019 11:51, Grahame Grieve wrote:
> > I got no response to this. I presume that mean that t
I got no response to this. I presume that mean that this is a stupid
question, but I'm afraid I don't understand why
Grahame
On Mon, Jan 14, 2019 at 11:45 PM Grahame Grieve <
grah...@healthintersections.com.au> wrote:
> Hi
>
> I have a 64bit windows application th
Hi
I have a 64bit windows application that uses openSSL, and I am using the
indy distribution from https://indy.fulgan.com/SSL/. This makes the file
names of the openssl dlls libeay32.dll and ssleay32.dll (even though they
are 64bit). Other distributions use other names (libcrypto-XX-x64.dll etc)
I can't find any documentation as the exact format of sig produced by
EVP_SignFinal when using a DSA key. It's 71 bytes, but 71 bytes of
what?
thanks
Grahame
--
-
http://www.healthintersections.com.au /
grah...@healthintersections.com.au / +61 411 867 065
___
11 matches
Mail list logo