Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Chris Ridd
On 30/9/03 10:55 pm, Paul Bearer <[EMAIL PROTECTED]> wrote: > Hi Chris, > > Thank you for your quick response. I love the intricacies of ASN.1 :) > > My real goal here is to be able to enocode these SubjectAltName structures. > Would you > have any insight on the best way to create a structure

Re: aproximate search and sorted results

2003-10-01 Thread Peter Lavender
* Peter Lavender ([EMAIL PROTECTED]) wrote: Not great replying to yourself, but just for the archive: > I've been thinking about this for a little while now, but haven't hit on a > suitable solution. > > The DSA I'm querying allows an approximate search, which uses a synonym > lookup. So as an

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Graham Barr
On 1 Oct 2003, at 9:05, Chris Ridd wrote: On 30/9/03 10:55 pm, Paul Bearer <[EMAIL PROTECTED]> wrote: OK, and it turns out that the extension value really *is* encapsulated inside an OCTET STRING. (Typical X.509 brokenness.) Your value isn't actually a SubjectAltName extension, it is an Extension

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Chris Ridd
On 1/10/03 12:47 pm, Graham Barr <[EMAIL PROTECTED]> wrote: > On 1 Oct 2003, at 9:05, Chris Ridd wrote: >> my $exts = $asn->find("Extensions"); >> my $san = $asn->find("SubjectAltName"); >> >> my $e = $exts->decode($binSan); >> # So we look at the first extension, and decode that as a >> SubjectAl

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Graham Barr
On 1 Oct 2003, at 18:10, Chris Ridd wrote: extnValue [UNIVERSAL 4] EXPLICIT ANY DEFINED BY extnID But that causes a parse error as it is expecting the tag to have the constructor bit set :( Maybe I could add an extension so we can write extnValue [UNIVERSAL 4] CONTAINING ANY DEFINED BY extnID

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Chris Ridd
On 1/10/03 6:58 pm, Graham Barr <[EMAIL PROTECTED]> wrote: > On 1 Oct 2003, at 18:10, Chris Ridd wrote: >>> extnValue [UNIVERSAL 4] EXPLICIT ANY DEFINED BY extnID >>> >>> But that causes a parse error as it is expecting the tag to have the >>> constructor bit set :( >>> >>> Maybe I could add an

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Graham Barr
On 1 Oct 2003, at 18:58, Graham Barr wrote: On 1 Oct 2003, at 18:10, Chris Ridd wrote: extnValue [UNIVERSAL 4] EXPLICIT ANY DEFINED BY extnID But that causes a parse error as it is expecting the tag to have the constructor bit set :( Maybe I could add an extension so we can write extnValue [UNI

Re: Password change in LDAP

2003-10-01 Thread Christopher A Bongaarts
In the immortal words of Dan Swanson: > I have a Perl script using Net::LDAP to create new accounts in > Microsoft Active Directory. Everything is working well except the > password change (see output below). I am attempting to perform a > ldap->modify(replace) which works well for other attribute

Re: Encoding/Decoding a subjectAltName using Convert::ASN1?

2003-10-01 Thread Simon Wilkinson
Graham Barr wrote: So you need to hold a mapping table for the OIDs <-> Type, and a way to define how the inner thing is embedded. The code todo that is already in C::ASN1, you do it like $asn->registeroid('2.5.29.17' => $asn->find('SubjectAltName')); Take a look in t/14any.t in the distribu