Vadim Fedukovich schrieb:
On Tue, Jun 11, 2002 at 01:46:40PM +0200, Michael Bell wrote:
Hi,
I start a simple implementation of othername only for strings in the
subject alternative name. Actually I have a problem with the resolving
of the ASN1_TYPE.
OTHERNAME is defined like this
On Wed, Jun 12, 2002 at 09:07:40AM +0200, Michael Bell wrote:
Vadim Fedukovich schrieb:
On Tue, Jun 11, 2002 at 01:46:40PM +0200, Michael Bell wrote:
Hi,
I start a simple implementation of othername only for strings in the
subject alternative name. Actually I have a problem with
Hi,
I read RFC 3280 4.2.1.7 again.
OtherName ::= SEQUENCE {
type-idOBJECT IDENTIFIER,
value [0] EXPLICIT ANY DEFINED BY type-id }
Does EXPLICIT ANY DEFINED BY type-id mean that the software (e.g.
OpenSSL) must know which ASN1-type does the type-id require?
If the
[[EMAIL PROTECTED] - Tue Jun 11 19:53:21 2002]:
Hello,
I'm getting the following error when I try and build openssh-0.9.6d
while running the make command:
cc -I.. -I../.. -I../../include -KPIC -DTHREADS -D_REENTRANT
-DDSO_DLFCN
-DHAVE_DLFCN_H -xtarget=ultra -xarch=v8plus -xO5
Gang. It is a little uncool to be having a long lengthy discussion of
someone's supported code without involving them in the discussion. As
it turns out all of the issues that have been addressed in this thread
related to C-Kermit had already been handled in the C-Kermit Daily
builds.
Thanks for the reply, there's a weird line in the math.h file #include
math.h, my c++ is not good, so I don't know what it means. I made a
local copy and commented out the line and it built successfully. Thanks
for your reply.
Regards,
Jamie Lipinski
Lutz Jaenicke via RT wrote:
[[EMAIL
OtherName ::= SEQUENCE {
type-idOBJECT IDENTIFIER,
value [0] EXPLICIT ANY DEFINED BY type-id }
It means that the type-id OID defines the datatype of the value. Think
of it as a union.
An alternative scheme would be to make the value be OCTET STRING, but
then you'd
On Wed, Jun 12, 2002 at 09:22:22AM -0400, Jeffrey Altman wrote:
Gang. It is a little uncool to be having a long lengthy discussion of
someone's supported code without involving them in the discussion. As
it turns out all of the issues that have been addressed in this thread
related to
Sorry for not including you into the discussion. I only cared about the
problem itself, which also pops up in mod_ssl, so I didn't even realize
that we were talking about your package.
Anyway:
NID_uniqueIdentifier _may_ be re-enabled at some point in the future
with its original meaning
Rich Salz schrieb:
OtherName ::= SEQUENCE {
type-idOBJECT IDENTIFIER,
value [0] EXPLICIT ANY DEFINED BY type-id }
It means that the type-id OID defines the datatype of the value. Think
of it as a union.
So the software must now the datatypes of all used OIDs
hi,
I want to send a signed email whichhave file
attachment.
I want to this functionin Perl
language.
any one can help me?
Mehdi Jabalameli [EMAIL PROTECTED]ce.sharif.edu/~jabalameli
Michael Bell wrote:
Rich Salz schrieb:
OtherName ::= SEQUENCE {
type-idOBJECT IDENTIFIER,
value [0] EXPLICIT ANY DEFINED BY type-id }
It means that the type-id OID defines the datatype of the value. Think
of it as a union.
So the software must now the
I remember mentioning this a while back, but don't think anything
ever came from it.
Are there any plans to add convenience functions for the hashes
specified in draft-ietf-pkix-certstore-http? (This proposed
document provides some implementation details for RFC2585, and
basically maps a URL of
Hello,
the callback I set with SSL_CTX_set_client_cert_cb() is never called, even
though SSL_CTX_get_client_cert_cb(), if called afterwards, returns a
non-NULL-value. I use OpenSSL 0.9.7 beta 1.
Any hints ?
Greetings
Erik
__
The manual page about SSL_CTX_set_client_cert_cb was simply wrong.
What in hell did I smoke when writing it? Or was it simply too late
at night??
Anyway, I have just checked in a new version:
If a certificate was already set, the client_cert_cb will never be
called. Once it is called and
As already pointed out in additional emails in openssl-dev:
* the change will stay in place, thus NID_x500UniqueIdentifier
will be the macro to use starting with OpenSSL 0.9.7
* I have not activated the original meaning of uniqueIdentifier and
it will not be done before 0.9.8 in order to
Hi:
I foundthere is something wrong in
crypto/asn1/asn1_mac.h and crypto/pkcs7/pk7_lib.c
in crypto/asn1/asn1_mac.h
the OLD code is:
#define M_ASN1_D2I_get(b,func)
\c.q=c.p; \if (func((b),c.p,c.slen) == NULL)
\{c.line=__LINE__; goto err; }
\c.slen-=(c.p-c.q);
and I
17 matches
Mail list logo
