possible Bug in OpenSSL - rfc 3161 - TSA service

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everybody, I do not know if this is the best place to discuss it, but I
would like to have your opinions on the best place to include Time Attribute
Certificate (TAC) into TST. By defult, the Thales timestamp system puts the
hash of TAC in the field signing certificate as discussed here. Here are
some questions: 
a) the insertion of the TAC in signing certificate is against the RFC 3161? 
b) If so, what would be the best place in TST to include the TAC or a
reference to it? 
c) What do you think of including the TAC or a reference to it in a non
critical extension of TSTInfo?

Best regards

custodio



--
View this message in context: http://openssl.6102.n7.nabble.com/possible-Bug-in-OpenSSL-rfc-3161-TSA-service-tp43128p62434.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux