Using the attached patch, OpenSSL can be built using lsbcc3 on Linux:
$ ./Configure linux-generic32-lsb
$ make CC=lsbcc3
Since this might be of general interest, could you please consider the
attached patch for future versions of OpenSSL?
Regards, Remo
diff -ru openssl-0.9.8g/Configure openss
Theodore Tso wrote:
I would suggest that the best way to do this is to *add* new mutator
functions (and accessor functions, where necessary) which applications
who care about ABI stability can use, and then document a set of
interfaces for which ABI stability is guaranteed. That could be a
relat
On Sun, Mar 16, 2008 at 09:21:05PM -0700, Michael Sierchio wrote:
> It is *so* difficult to critique something without seeming to
> criticize the work of others, so the following disclaimer applies.
> MUCH is owed to the developers and maintainers of OpenSSL --
> Mark, Ralf, Stephen, Ben, Lutz, Nil
and is written in C++.
I doubt that will happen. You'd alienate a lot of developers
out there and lose support of some systems, especially embedded
systems, which may not even have a C++ compiler. I don't think
there is any justification for C++.
-Brad
Theodore Ts'o wrote:
Reading through the mail archives, the problem, as I understand
it, is that OpenSSL is derived from a very old legacy codebase, with an
interface which relies on publically visible data structures which must
be accessed either directly, or via accessor macros. In so
Hi,
I'm writing this note to try to reopen a discussion that has
been going on for the last couple of years. Most recently, the
discussion was kicked off by Tracy Camp in November, 2006, and before
that in October, 2005.
Reading through the mail archives, the problem, as I unders
>For 0.9.9-dev I would prefer making the parameter (and hence the
>return type) in the X509_foo_get() functions const but I'm not
>sure if we should change this behaviour in 0.9.8-stable.
>Comments are welcome.
I think I had experimented with making things const at one point but had
concluded that
Camp, TracyX E wrote:
...
Comments, etc. welcomed.
I've committed one part of the patch (to OpenSSL_0_9_8-stable and the
cvs head). The changes in crypto/x509/ are little bit problematic IMHO
as it could require code changes in application using the existing
macros. For example if you have some
Ben Laurie wrote:
Camp, TracyX E wrote:
I really didn't hear much back on this topic, but what I did hear seemed
to support the approach I have been taking thus far. Please see my
previous message in this thread for the details.
So in hopes of moving this topic along in a practical sense, I
>How is that vast amount of software going to work under LSB, then?
LSB does not support all applications anyways (for example, anything
that has a direct kernel dependency is not a LSB application), and we
are not trying to do so here either. Instead I'm attempting to be able
to support somethi
Camp, TracyX E wrote:
>
>> I'm very much in favour of this. One comment, though - if you're going
>> to make structure opaque, then why not make them truly opaque by
>> removing their definitions from the public headers?
>
> In LSB they would be truly opaque. LSB works by producing a set of st
>
>I'm very much in favour of this. One comment, though - if you're going
>to make structure opaque, then why not make them truly opaque by
>removing their definitions from the public headers?
In LSB they would be truly opaque. LSB works by producing a set of stub
libraries and generated heade
Camp, TracyX E wrote:
>
> I really didn't hear much back on this topic, but what I did hear seemed
> to support the approach I have been taking thus far. Please see my
> previous message in this thread for the details.
>
> So in hopes of moving this topic along in a practical sense, I have
> a
ent by:
owner-openssl-dev cc
@openssl.org
Subj
I’d like to re-start some discussion about including
OpenSSL in LSB (acronym expansion: Linux Standards Base see: http://www.freestandards.org). There
is apparently general interest in seeing OpenSSL in LSB both for its SSL
functionality as well as its utility as a general cryptographic li
15 matches
Mail list logo
