I see the point. Thanks alot
On Tue, Jul 20, 2010 at 12:47 AM, Mounir IDRASSI
wrote:
> Hi,
>
> When calling RSA_private_encrypt with RSA_NO_PADDING, the input must have
> the same size as the RSA key modulus.
> In your case, you are supplying 20 bytes whereas it certainly needs more
> (for exam
Hi,
When calling RSA_private_encrypt with RSA_NO_PADDING, the input must
have the same size as the RSA key modulus.
In your case, you are supplying 20 bytes whereas it certainly needs more
(for example, for a 1024 bit key, input must be 128 bytes long). So, you
have to add some sort of paddi
On Mon, Jul 19, 2010, anhpham wrote:
>
> Hi all :x
> I encountered an error when using function RSA_private_encrypt with
> RSA_NO_PADDING option.
> I had an unsigned char array a with length = 20, RSA* r,
> unsigned char* sig = (unsigned char*) malloc(RSA_size(r)) and then I invoked
> function i
Hi all :x
I encountered an error when using function RSA_private_encrypt with
RSA_NO_PADDING option.
I had an unsigned char array a with length = 20, RSA* r,
unsigned char* sig = (unsigned char*) malloc(RSA_size(r)) and then I invoked
function int i = RSA_private_encrypt(20,a ,sign,r,RSA_NO_PADDI
Thanks a lot for the explanation Patrick, that did the trick!
On Fri, Jul 16, 2010 at 1:58 PM, Patrick Patterson <
ppatter...@carillonis.com> wrote:
> Hello Hugo:
>
> On July 16, 2010 02:31:53 pm Hugo Garza wrote:
> > Hello Stephen, thank you for your comment that made the verification
> pass.
>
On 19-07-2010 14:32, Jeffrey Walton wrote:
On Wed, Jul 14, 2010 at 6:42 AM, Jakob Bohm wrote:
On 14-07-2010 07:52, Jeffrey Walton wrote:
On Tue, Jul 13, 2010 at 3:04 PM, Jakob Bohmwrote:
[SNIP]
proponents of the RSA and DH algorithms said that the
number was wildly exaggerated and pr
On Wed, Jul 14, 2010 at 6:42 AM, Jakob Bohm wrote:
> On 14-07-2010 07:52, Jeffrey Walton wrote:
>>
>> On Tue, Jul 13, 2010 at 3:04 PM, Jakob Bohm wrote:
>>>
>>> [SNIP]
>>
> proponents of the RSA and DH algorithms said that the
> number was wildly exaggerated and proposed some much
> s
Hi all :x
I'm using OpenSSL 1.0.0 and I encountered a problem when using function
RSA_private_encrypt. I have an unsigned char array a[] with length = 20,
RSA* r, unsigned char* signature = (unsigned char*) malloc(RSA_size(r)).
Then I invoked function int i = RSA_private_encrypt ( 20, a, signature
On 16-07-2010 22:50, Mark Bishop wrote:
Thank you very much so far with all the input you have given me. I have
few more questions. I am going to have to give up on interfacing with
the Windows Crypto library and put openssl on my client as well.
However, my client will be running Windows CE 6.0
Hi again,
When i see the client certificate details using IE browser I see this on
the Authority Information Access Field
[1]Authority Info Access
Access Method=On-line Certificate Status Protocol
(1.3.6.1.5.5.7.48.1)
Alternative Name:
URL=http://ocsp.auc.cartaodecid
Hi to all, first of all a big thanks to everyone that so far helped me on all
the OCSP questions Ive had so far.
I still have a single problem when trying to validade client Certs using Apache
and a OCSP responder. Iam having this error on error log:
(I can successfully validate the cert if us
Hi to all.
can I use multiple SSLOCSPDefaultResponder directives in Apache in the hope
that Apache will try to contact all of them until one gives success with a
client Certificate?
if not, how can I configure Apache so It accepts (and test the revogation
status) certificates from multiple CA
Hummm, thanks for catching this this is not good news for us
I dont believe anyone on this CA will care for this, but I will try anyway.
Regards
Luis
> From: ppatter...@carillonis.com
> To: openssl-users@openssl.org
> Subject: Re: OCSP_basic_verify:certificate verify error ( Verify
>
Hi All,
My cc compiler is :
/usr/bin/cc:
$Revision: 92453-07 linker linker crt0.o B.11.61 070723 $
LINT B.11.11.20 CXREF B.11.11.20
HP92453-01 B.11.11.20 HP C Compiler
$ PATCH/11.00:PHCO_27774 Oct 3 2002 09:45:59 $
and use gmake to make the openssl.
I am not
14 matches
Mail list logo