One other issue though the base64 encoded string contains new line
character at the end.
is there a way through the api to not include it.
It is characteristic of openssl to insert linebreaks in both base64
and PEM encodings --- and to require them when it decodes data. If
for some r
One other issue though the base64 encoded string contains new line character
at the end.
is there a way through the api to not include it.
From: "k b" <[EMAIL PROTECTED]>
Reply-To: openssl-users@openssl.org
To: openssl-users@openssl.org
Subject: Re: Base64 encoding with BIO_new_mem_buf
Date: T
> thanks a lot for answering my question.. but is this the only way?
> it seems a bit overwhelming for me.. isn't there any other way?
> like any function we can call?
Rather than risking you screwing up security-critical code, why don't you
paste the part of the code that sets the validity and
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Naveen Rawat
Sent: Saturday, July 07, 2007 9:51 AM
To: openssl-users@openssl.org
Subject: Certificate profile issue
Hi all,
I am trying to create a common CA hierarchy like :
[root]
|
|-[C
Thanks for your quick answer David, I will think about use IDEA instead
of AES (i believe that´s no problem about commercial use with AES).
Regards.
David Schwartz escribió:
I´m adapting a PKCS#11 module for using it on Ubuntu Feisty. I had it
perfectly working on Ubuntu Dapper, but when I comp
Hi,
I tried to learn this question from manpages and from Google searches,
but it didn't helped, I even tried to read the sources, but I'm not
not in it enough. :(
Is there any drawbacks of calling OpenSSL_add_all_digests more than
once. The problem is in a patch for a modularized application
(l
Hi,
I built a test code to fetch the custom information from X509_add_ext().
The test codes are as following:
codes for fetching extension
static char *get_distribution_point(X509 *cert) {
int extcount, i, j;
const char*extstr;
CONF_V
Hello
I try to verify
file>Test500.decrypt.data
Content-Type: multipart/signed;
boundary="=_Part_1121_5124355.1183362911134";
protocol="application/pkcs7-signature"; micalg="sha1"
--=_Part_1121_5124355.1183362911134
Content-Type: application/EDIFACT; name=391926000.t
thanks a lot for answering my question.. but is this the only way? it seems
a bit overwhelming for me.. isn't there any other way? like any function we
can call?
thanks
On 7/13/07, Jim Fox <[EMAIL PROTECTED]> wrote:
On Jul 12, 2007, at 9:29 PM, imin macho wrote:
> hi...
>
> i'm a noob in ope