[xmlsec] xmlsec 's future
t.noguchi at pfu.fujitsu.com
Sun Apr 23 19:47:38 PDT 2006
You and the OASIS published XAdES and EPM document:
# But I'm not a member of OASIS...
Did you create a Token of "XML Timestamp" by xmlsec?
My goal is make the XAdES plugin of OpenOffice.org with RFC3161 TimeStamp.
What do you think about this idea?
# Current TSA's only support RFC3161 TimeStamp.
If you possibiy want to support EPM into the OpenDocument Format, I have
But Japanese PostOffice do not support EPM. And the specification were
with the Office documents.
ed.shallow at rogers.com wrote:
> On your last question, RFC3161 timestamps are by definition PKCS7
> ASN1 binary signatures. The only XMLDSIG-based timestamp I am aware of
> is from the OASIS DSS Technical Committee at
> I have used xmlsec to create dss:Timestamps without problems.
> ----- Original Message ----
> From: 野口隆弘 <t.noguchi at pfu.fujitsu.com>
> To: Aleksey Sanin <aleksey at aleksey.com>
> Cc: tnoguchi <tnoguchi at bh.wakwak.com>; t.noguchi
> <t.noguchi at jcsinc.co.jp>; xmlsec at aleksey.com; machida at jcsinc.co.jp
> Sent: Friday, April 21, 2006 12:10:01 AM
> Subject: [xmlsec] xmlsec 's future
> Hi, Aleksey,
> What do you think future image of xmlsec?
> You did update hash algorithms with OpnSSL.
> Is this enhancement were measures for NIST sha-1 announce?
> But the CAs and IC card vendor could not upgrade algorithms soon.
> Because it depend on OS function and IC chip. So, the TSA did upgrade
> algorithms and
> wrap signature by new algorithms timestamp.
> www.e-timestamp.com and www.pfutsa.net <http://www.pfutsa.net/>
> already support RSA2048bit and SHA-2
> algorithms timestamp. The pfutsa.net is japanese site....
> And TSAs has SDK for own service.
> Will you support RFC3161 timestamp on xmlsec?
> xmlsec mailing list
> xmlsec at aleksey.com
More information about the xmlsec