This is a non-issue; they are two different ways of saying
the same thing.
The AIX description is the same one all Unix systems with
select() have used
since... 4.2BSD. I don't recall if 4.1 had select() or not.
Think about it. The fdset is a bit field. The nfds parameter
tells select
Ahhh,
The CU usage is *always* going to go to 100 percent, no matter how low the priority
is. The real question should have been when I sign or encrypt, the operation adversly
affects other important processes because the s/e operation is consuming needed cpu
cycles, what can I do about this.
I waited for any others to comment but no-one did, so here's a couple of cents.
While it might make sense in a server enviroment to have such a malloc, complete
with memory pools and whatnot, it still doesn't forgive an application from checking
malloc return codes and dealing with a no-memory
I'm not on the dev team or anything, but I don't understand how you could have *ever*
successfully encrypted multiple streams with the same EVP context??? Just the IV's
alone would have been screwed up for CBC ciphers and stream ciphers like RC4 would
completely break.
Unless, of course, you
Good idea except the same mutate must also be performed on the other end or you'll
end up with a key mismatch. We don't always run OpenSSL on both ends.
-lee
-Original Message-
From: James Yonan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 02, 2002 6:55 PM
To: [EMAIL PROTECTED]
I see nothing incorrect in the padding.
The code pads as described in the rfc.
The pkcs 5 rfc (2989) states(page 11)
4. Concatenate M and a padding string PS to form an encoded
message EM:
EM = M || PS ,
where the padding string PS consists of
Don't know if the dev list is the right place for this question... please repost if it
isn't.
I'm trying to build a static library on win32 (using ms\nt.mak) and while that
succeeds just fine, when I link the ssleay32.lib and libeay32.lib(combined, about 2.7
Mbytes) to my application, I get
The problem you are running into (probably) is that an RSA key cannot
encrypt data that is larger than the key size. In your case, a 64 bit RSA key
would not be able to encrypt the signature hash since the hash is 128 bits
long.
As a security point, RSA keys less than 512 bits are generally
Hi,
I'm sure this is a fairly simple and probably common request.
I want to include the ssl cert and private key (copied, pem, from the files) in my
program as static variables (to avoid having files in my file-less application). I'm
staring at SSL_CTX_use_certificate_file() and the other
