From 46edf96174ba0729b333bb62cdba912fc8f3907b Mon Sep 17 00:00:00 2001 From: Lev Walkin Date: Mon, 28 Feb 2005 15:34:47 +0000 Subject: [PATCH] restructuring --- FAQ | 35 ++++++++++++----------------------- 1 file changed, 12 insertions(+), 23 deletions(-) diff --git a/FAQ b/FAQ index d652b7f8..934e1d73 100644 --- a/FAQ +++ b/FAQ @@ -1,4 +1,16 @@ +Q: How to build a simplest BER (XER) encoder or decoder? +A: + + Please see "Examples" section of ./doc/asn1c-usage.pdf + + Also, try the following to build the X.509v3 parser: + + cd ./examples/sample.source.PKIX1 + make + ./x509dump -h + + Q: Your compiler supplies a der_encode() procedure. How do I encode BER? A: The DER (and CER) are stricter subsets of a more generic BER encoding @@ -13,29 +25,6 @@ A: Distinguished Encoding Rules (DER)" -Q: I've tried doing ./asn1c/asn1c -P examples/*PKIX*93*, but compiler spits - several fatal failures and exits. -A: - The old (RFC2459) PKIX1 specifications used ASN.1 Information Object - Classes, which is arguably one of the most complex ASN.1 concepts. - - The asn1c parser and fixer subsystems currently understand most of - IOC syntax, but the compiler can cope with only the very basic - IOC semantics. - - The goal of asn1c is to adequately support the practically necessary - subset of IOCs to compile PKIX1 and other real-world specs, - but this milestone isn't yet reached. Please contact me in case - you have special requirements, we can work it out. - - However, the asn1c compiler is able to understand the newer PKIX1 - ASN.1 specs, contained in RFC3280, which obsoletes RFC2459. - To compile the sample X.509 certificate dump utility, try this out: - - cd ./examples/sample.source.PKIX1 - make - ./x509dump -h - -- Lev Walkin