Does anyone know of any documentation or examples on how to use a custom
elliptic curve with ECDSA and ECDH of openssl's crypto library?
It doesn't look like support of custom curves is built-in. So, I have
tried to duplicate what was done with built-in curves in
crypto/ec/ec_curve.c to
Hi Marek,
m1 has binary data, not string.
This data may have embeded 0x00 (look at your output above) and strcat
can not copy data in good place (to bytes before end instead of end of md1).
Use memcpy, does not relay of strlen() on such data too.
I check for the output and the inner hash
Hi Marek,
I arrived to do inner/outer hash with success.
Next step: store binary result into char static :)
Best regards
On Mon, Apr 14, 2008 at 5:42 PM, Badra [EMAIL PROTECTED] wrote:
Hi Marek,
m1 has binary data, not string.
This data may have embeded 0x00 (look at your output above)
Hi ,
can any one knows what Max size of data or file can be signed or encrypted
using PKCS7_sign() and PKCS_encrypt funtions.
If my file is a size of one GB (or 100 gb)can this funtions work properly
with out any errors , or do I need to use low level funtions.
--
--Best Regards
Shankar
Welling, Conrad Gerhart wrote:
#12#3#4#5#6#7#8
Problem description: openssl-fips-1.1.2 make install fails in
fips-1.0/Makefile for hpux64-ia64-cc, HP-UX 11.
OK, I think I'll implement my own BIO. My C is good, although not
brilliant, but I can do it. What stopped me from trying that approach
in the first place was that the BIO* functions are so many and
that I don't know which ones do I actually *need* to reimplement (that
is, which ones is the
Is there any reference of what do the different members of the BIO
objects mean? method, ptr, next_bio and prev_bio are pretty obvious,
but the rest, I don't know, and I haven't been able to find any
details out there.. I'll keep googling, but if anyone knows of a good
detail out there, please
On Tue, Apr 15, 2008, Tomas Neme wrote:
Is there any reference of what do the different members of the BIO
objects mean? method, ptr, next_bio and prev_bio are pretty obvious,
but the rest, I don't know, and I haven't been able to find any
details out there.. I'll keep googling, but if anyone
Most of them you don't need to worry about. I'd suggest looking at the fd BIO
and copy some of the functionality from that.
OK, I will. I just wondered because mem_new (the new method of
BIO_s_mem) sets shutdown = 1 ; init = 1; num = -1 and rtcp does init =
1 ; num = 0 ; flags = 0 ; so I'd
Stephen:
Most of them you don't need to worry about. I'd suggest looking at the fd
BIO
and copy some of the functionality from that.
I also need to know which of the BIO_CTRL_* params do I have to
implement in my _ctrl function. Is there a reason why you said to look
at the fd BIO
On Tue, Apr 15, 2008 at 04:22:03PM -0300, Tomas Neme wrote:
Stephen:
Most of them you don't need to worry about. I'd suggest looking at the
fd BIO
and copy some of the functionality from that.
I also need to know which of the BIO_CTRL_* params do I have to
implement in my
It would seem that the socket BIO handles the socket abstraction, but
it does not handle calls to BIO_S_CONNECT. Actually, a grep for
BIO_S_CONNECT returns only bss_conn.. why is this? shouldn't sockets
have a call to connect too?
sorry, I forgot that you create the BIO_socket with the
Well, Steve, if you had no problem, I'm inclined to believe that I am in
error and that I didn't review the occurrence properly before reporting it.
I'll report back when I've reviewed the issue again by confirming it's
occurrence (start-from-scratch) and I'll try v1.2. Thanks.
-Original
Welling, Conrad Gerhart wrote:
Well, Steve, if you had no problem, I'm inclined to believe that I am in
error and that I didn't review the occurrence properly before reporting it.
I'll report back when I've reviewed the issue again by confirming it's
occurrence (start-from-scratch) and I'll
14 matches
Mail list logo
