In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 22:05:07 -0700, Dan Kegel
<[EMAIL PROTECTED]> said:
dank> http://www.gnu.org/software/gnutls/
dank> exposes two APIs: the OpenSSL api (I gather?), and its own.
About the OpenSSL API, this page answers part of the question.
http://www.gnu.org/
What is the benefit of adding parts of OpenSSL to the LSB now?
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
__
Andy Polyakov via RT wrote:
Summary can be found at http://cvs.openssl.org/chngview?cn=14145. Point
is that I assumed that RC4_KEY structure initialized by RC4_set_key is
passed down to RC4 verbatim in its original memory location, while
OpenSSH takes freedom to swap the structures initialized in
In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 22:07:04 -0700, Rodney
Thayer <[EMAIL PROTECTED]> said:
rodney> with openssl-0.9.8-beta6, on fedora core 3 on an intel box,
rodney> for example:
rodney>
rodney>"./config no-shared no-idea no-rc5 -d" FAILS
Does it still fail in the same pla
Richard Levitte - VMS Whacker wrote:
Quite honestly, even though I'm quite an enthusiastic OpenSSL
developer for years and have been for years (since it started,
really), I can't really recommend OpenSSL as an LSB candidate from
that point of view, as it stands today. Every "major upgrade" (whic
Richard Levitte - VMS Whacker wrote:
In message <[EMAIL PROTECTED]> on Tue, 28 Jun 2005 09:29:54 -0700, Rodney Thayer
<[EMAIL PROTECTED]> said:
rodney> 'make test' never works. in the EC test, it runs a long time
rodney> (tracing the output gives multiple gigabytes of text, it seems
rodney> to
Yes, simple casting isn't going to result in much other that emergency foot
surgery. It's been some time since I did any WinCE work, but I seem to
recall that there is only the W variant of most functions on Windows CE.
Windows CE, if my memory is correct, is Unicode-only. The original patches
th
In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 17:44:38 -0700, "Banginwar,
Rajesh" <[EMAIL PROTECTED]> said:
rajesh.banginwar> Do you or anyone on this project have data
rajesh.banginwar> suggesting which APIs are candidates for LSB
rajesh.banginwar> inclusion both from demand and stability p
Hi Frank,
I've got a lot going on right now, meaning that I don't have time to look at
this in detail. Generally speaking though, the goal of wcecompat was to
fill the gap between what the Windows CE C Runtime Library offered and what
a full ANSI/Posix Runtime Library should offer. Time constrai
On June 29, 2005 08:44 pm, Banginwar, Rajesh wrote:
> So far from the preliminary analysis that we have done (by looking at
> some of the OSS applications) we see both libssl and libcrypto being
> used. E.g. from libcrypto I find functions in EVP, RSA, MD5 and DSA
> sets more commonly used than oth
> -Original Message-
> From: Geoff Thorpe [mailto:[EMAIL PROTECTED] On Behalf
> Of Geoff Thorpe
> Sent: Wednesday, June 29, 2005 5:45 PM
> To: openssl-dev@openssl.org
> Cc: Banginwar, Rajesh
> Subject: Re: Considering SSL and Cryto libraries for LSB
>
> On June 29, 2005 05:50 pm, Banginwa
On June 29, 2005 05:50 pm, Banginwar, Rajesh wrote:
> As part of LSB standardization process, we look at the interfaces and
> corresponding data types and make it part of the specification. If the
> data types are expected to change and the interfaces do not hide them,
> then that part of the libra
On Wed, Jun 29, 2005, Dan Nuffer wrote:
> Dr. Stephen Henson wrote:
> >This means that changing this in the short term is likely to cause
> >widespread
> >application breakage which wouldn't be too popular :-(
> >
>
> Speaking as an application developer, I would willingly go through a
> one-ti
On Thu, Jun 30, 2005, Peter Waltenberg wrote:
> IBM has already done this in creating it's FIPS certified crypto. code
> which is layered on top of OpenSSL.
>
> In our case we can guarantee that IBM code only uses our restricted subset
> of the OpenSSL API.
> Unfortunately you'll need to suppor
Dr. Stephen Henson wrote:
This means that changing this in the short term is likely to cause widespread
application breakage which wouldn't be too popular :-(
Speaking as an application developer, I would willingly go through a
one-time source code upgrade to achieve binary compatiblity. Tha
IBM has already done this in creating
it's FIPS certified crypto. code which is layered on top of OpenSSL.
In our case we can guarantee that IBM
code only uses our restricted subset of the OpenSSL API.
Unfortunately you'll need to support
the older API's to support legacy applications and in won'
with the single "openssl.pc" pkg-config file we can only
link witl -lcrypto -lssl -ldl. it would be better to provide
a libcrypto.pc and a libssl.pc so we can create apps and libs,
that link with libcrypto only.
__
OpenSSL Pro
On Wed, Jun 29, 2005, Banginwar, Rajesh wrote:
> As part of LSB standardization process, we look at the interfaces and
> corresponding data types and make it part of the specification. If the
> data types are expected to change and the interfaces do not hide them,
> then that part of the library m
As part of LSB standardization process, we look at the interfaces and
corresponding data types and make it part of the specification. If the
data types are expected to change and the interfaces do not hide them,
then that part of the library may not be a candidate for LSB.
Given this, I am just wo
On Wed, Jun 29, 2005, Banginwar, Rajesh wrote:
> We recently started looking at some of Desktop specific libraries for
> including them as part of next LSB (Linux Standard Base
> www.linuxbase.org) release. This is part of the effort in the newly
> formed Desktop working group in LSB to focus on t
We recently started looking at some of Desktop specific libraries for
including them as part of next LSB (Linux Standard Base
www.linuxbase.org) release. This is part of the effort in the newly
formed Desktop working group in LSB to focus on the Desktop Linux
applications.
As a part of this effor
On Mon, Jun 27, 2005, Jrgen Hovland wrote:
> Hi
>
> Does anyone know what to do with this? Im trying to compile a masm version.
> Thank you.
>
> cl /Fotmp32dll\ec_asn1.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox
> /O2 /
> Ob2 /Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND
[EMAIL PROTECTED] - Wed Jun 29 17:43:06 2005]:
> > So the bug report can be removed, right?
>
> Yes, the report can be removed. It is not a bug.
Thanks.
Ticket resolved.
--
Richard Levitte
[EMAIL PROTECTED]
__
OpenSSL Proje
> So the bug report can be removed, right?
Yes, the report can be removed. It is not a bug.
> (and *please* keep [EMAIL PROTECTED] among the recipients. It's quite
> hard to follow history in the database when people keep skipping that
> address)
Apologies.
nagendra
> So the bug report can be removed, right?
Yes, the report can be removed. It is not a bug.
> (and *please* keep [EMAIL PROTECTED] among the recipients. It's quite
> hard to follow history in the database when people keep skipping that
> address)
Apologies.
nagendra
__
Richard Levitte - VMS Whacker wrote:
In message <[EMAIL PROTECTED]> on Wed, 29 Jun 2005 06:42:59 +0200, Karsten Ohme
<[EMAIL PROTECTED]> said:
widerstand> will there be some day, when the the OpenSSL source code
widerstand> is documented in a some way? In all source files,
widerstand> explanati
26 matches
Mail list logo