Canonical XML & XML Schema
Comments on 22 June Version...
- Re: Comments on 22 June Version...
- RE: Comments on 22 June Version...
- RE: Comments on 22 June Version...
- RE: Comments on 22 June Version...
De-referencing a URI
Consensus re exclusive canonicalization
Exclusive Canonicalization: A trivial problem
- RE: Exclusive Canonicalization: A trivial problem
- Re: Exclusive Canonicalization: A trivial problem
- RE: Exclusive Canonicalization: A trivial problem
- RE: Exclusive Canonicalization: A trivial problem
Exclusive Canonicalization: A trivial problem
XML Reference implementation
LF in the middle of a name in X509IssuerName and X509SubjectName
RSA Interoperability Results
Poll on Exclusive Canonicalization
- Re: Poll on Exclusive Canonicalization
- Re: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- Re: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- Re: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- Re: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
- RE: Poll on Exclusive Canonicalization
A Full Proposal for Adding Interoperatble Signatures for Protocol-like Applications to XMLDSIG
RE: Signature Portability, CanonicalizationMethod, etc.
Canonical Standards and XMLDsig
Signature Portabilit, CanonicalizationMethod, etc.
- Re: Signature Portabilit, CanonicalizationMethod, etc.
- Re: Signature Portabilit, CanonicalizationMethod, etc.
<X509Data> grouping restrictions
Change to Ed Simon's status
XML Schema base64Binary simple type
- Re: XML Schema base64Binary simple type
- Re: XML Schema base64Binary simple type
- Re: XML Schema base64Binary simple type
- Re: XML Schema base64Binary simple type
- Re: XML Schema base64Binary simple type
RE: DSAKeyValue text - inferring trust from just a PK
DSAKeyValue text
- Re: DSAKeyValue text
- RE: DSAKeyValue text
- RE: DSAKeyValue text
- RE: DSAKeyValue text
- RE: DSAKeyValue text
- Re: DSAKeyValue text
- RE: DSAKeyValue text
RE: 3.2.1 Reference Validation - Section has been confused with S ignature Validation
signer authentication
Empty SignedInfo elements properly canonicalized in examples?
- RE: Empty SignedInfo elements properly canonicalized in examples?
- Re: Empty SignedInfo elements properly canonicalized in examples?
- RE: Empty SignedInfo elements properly canonicalized in examples?
- RE: Empty SignedInfo elements properly canonicalized in examples?
HMACOutputLength interop?
Re: 3.2.1 Reference Validation - Section has been confused with Signa ture Validation
ANN: The W3C XML Processing Model Workshop
More than one signer - again
RE: Base64 -- do we really want/need line breaks every 76 cha racters?
RE: Base64 -- do we really want/need line breaks every 76 characters?
signature portability / C14N / inherited namespaces, etc.
- Re: signature portability / C14N / inherited namespaces, etc.
- Re: signature portability / C14N / inherited namespaces, etc.
- Proposal: Text for signature portability / C14N / inherited namespaces, etc.
- Re: Proposal: Text for signature portability / C14N / inherited namespaces, etc.
- Re: Proposal: Text for signature portability / C14N / inherited namespaces, etc.
- Re: Proposal: Text for signature portability / C14N / inherited namespaces, etc.
Re: dropping MgmtData?
Fwd: Re: Erratum in section 1.1 of Canonical XML
3.2.1 Reference Validation - Section has been confused with Signa ture Validation
Looking for an article about XML Signature
RE: Base64 -- do we really want/need line breaks every 76 charact ers?
RE: Base64 -- do we really want/need line breaks every 76 charact ers?
Re: Base64 -- do we really want/need line breaks every 76 characters?
- Re: Base64 -- do we really want/need line breaks every 76 characters?
- Re: Base64 -- do we really want/need line breaks every 76 characters?
Base64 -- do we really want/need line breaks every 76 characters?
- RE: Base64 -- do we really want/need line breaks every 76 characters?
- RE: Base64 -- do we really want/need line breaks every 76 characters?
Fwd: Call for Participation: XML Key Management Services Workshop, 19 July 2001
style sheet for CR-xmldsig-core-20010419
Comments for CR-xmldsig-core-20010419
[Review] Conformance in XML signature
DTD-less id('object-3') -- what am I missing?
XML Signatures and binary files
- Re: XML Signatures and binary files
- RE: XML Signatures and binary files
signature portability / C14N / inherited namespaces
- Re: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
- RE: signature portability / C14N / inherited namespaces
KeyName white space
- Re: KeyName white space
- Re: KeyName white space
- AW: KeyName white space
- Re: AW: KeyName white space
- Re: AW: KeyName white space
- AW: AW: KeyName white space
- Re: AW: AW: KeyName white space
- Re: AW: AW: KeyName white space
- DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- Re: DName encoding (was:KeyName white space)
- RE: DName encoding (was:KeyName white space)
- RE: DName encoding (was:KeyName white space)
- RE: DName encoding (was:KeyName white space)
- RE: DName encoding (was:KeyName white space)
Re: Why is it extrictly obligatory the use of CanonicalizationMethod?
General Question
X509CRL discord
Comments/Questions about the XML-Signature spec
Erratum in summary list of Canonical XML spec
[Fwd: Erratum in section 2.1 of Canonical XML]
Erratum in section 1.1 of Canonical XML
- RE: Erratum in section 1.1 of Canonical XML
- RE: Erratum in section 1.1 of Canonical XML
- RE: Erratum in section 1.1 of Canonical XML
- RE: Erratum in section 1.1 of Canonical XML
- RE: Re: Erratum in section 1.1 of Canonical XML
KeyInfo interoperability
More than on signature
I-D ACTION:draft-eastlake-xmldsig-uri-01.txt
XML Signature Interoperability.
Last Call: XML-Signature Syntax and Processing to Draft Standard
SUBSCRIBTION
Need Website Traffic? We Generate It!
updated additional URIs draft
Subscribtion
I-D ACTION:draft-ietf-xmldsig-core-2-00.txt
I-D ACTION:draft-eastlake-xmldsig-uri-00.txt
Fwd: Revised XML-Signature Syntax and Processing Candidate Recommendation: Call for Implementation Ends 19 May 2001
Problem: referring to a complete sub-tree using XPath
Minimal Canonicalization Removed
Two slight tweaks to schema
additional XMLDSIG URIs
- RE: additional XMLDSIG URIs
- RE: additional XMLDSIG URIs
- RE: additional XMLDSIG URIs
- Re: additional XMLDSIG URIs
- Re: additional XMLDSIG URIs
- RE: additional XMLDSIG URIs
- Re: additional XMLDSIG URIs
- RE: additional XMLDSIG URIs
- Re: additional XMLDSIG URIs
MS crypto API and Java security API (KeyValue)
xml-c14n: Typo Error
ds:CryptoBinary vs. base64Binary
Java APIs for XMLDSIG
new example signature
KeyInfo type URIs
Misspelled xPointer in current draft
Implementors: Please Update Interop Matrix
- Re: Implementors: Please Update Interop Matrix
- Re: Implementors: Please Update Interop Matrix
- RE: Implementors: Please Update Interop Matrix
- RE: Implementors: Please Update Interop Matrix
- AW: Implementors: Please Update Interop Matrix
- Re: Implementors: Please Update Interop Matrix
- Re: Implementors: Please Update Interop Matrix