Geoff Thorpe wrote:
Hey there,
On Mon, 19 Feb 2001, tc lewis wrote:
you know, these commit mails are really nice. seriously. any chance
someone could forward over the openssl cvs repository's loginfo file
(and/or whatever else may be involved)?
Why not just rsync the CVS
Came across these while doing a typo pass in FreeBSD.
Kris
Index: CHANGES.SSLeay
===
RCS file: /mnt/ncvs/src/crypto/openssl/CHANGES.SSLeay,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 CHANGES.SSLeay
--- CHANGES.SSLeay
It is actually not possible. The best you can hope is to use openssl as
an API to develop a WTLS library. WTLS certificate does not use ASN1 in
fact.
It might exist some opensource project doing already this.
Marc.
Amit Chitale wrote:
Hello ,
I am trying to find out if I can use OpenSSL to
Hey there,
On Tue, 20 Feb 2001, Bodo Moeller wrote:
On Tue, Feb 20, 2001 at 09:37:19AM +, Ben Laurie wrote:
Geoff Thorpe wrote:
BTW: This is a *large* data transfer (around 80Mb at last count) - but after
it's done the first time, updates tend to be quite minimal.
I presume he
Hi there,
Um, actually this isn't right ...
On Tue, 20 Feb 2001 [EMAIL PROTECTED] wrote:
[snip]
Modified:crypto/objects o_names.c
[snip]
@@ -67,8 +67,8 @@
{
MemCheck_off();
name_funcs = OPENSSL_malloc(sizeof(NAME_FUNCS));
-
Ah ...
On Tue, 20 Feb 2001, Geoff Thorpe wrote:
@@ -67,8 +67,8 @@
{
MemCheck_off();
name_funcs = OPENSSL_malloc(sizeof(NAME_FUNCS));
- name_funcs-hash_func = lh_strhash;
- name_funcs-cmp_func = strcmp;
+
From: Geoff Thorpe [EMAIL PROTECTED]
geoff Ah ...
geoff
geoff On Tue, 20 Feb 2001, Geoff Thorpe wrote:
geoff
geoff @@ -67,8 +67,8 @@
geoff{
geoffMemCheck_off();
geoffname_funcs = OPENSSL_malloc(sizeof(NAME_FUNCS));
geoff -
Hallo,
has the EVP interface (sign/verify) a way to specify
the padding for the signed data ?
And I would like to add a way to support other padding types
(something like
RSA_add_padding(..., int adding, int (*fct)(unsigned char *to,
int tlen, unsigned char *from,int flen))
)
By
Goetz
--
Hi,
I'm trying to verify the Openssl SHA1 implementation uses test vectors
and their known answers
published by Nist. When I run the test I'm not getting the expected
results.
Specifically, the SHA1 hash of
the following eight bytes
0x00, 0x00, 0xFF, 0x00, 0x00, 0xFF, 0x00, 0x00
is supposed
