Apache OpenOffice (AOO) Bugzilla – Issue 20883
Q-PCD Digital Signatures and Encryption
Last modified: 2005-01-20 15:23:32 UTC
Task tracking system for Childs PLEASE CREATE CHILD-TASKS IN ISSUEZILLA! Source Erwin Category General Security Digital Signatures and Encryption Product Requirement An average user with no specific knowledge about security technologies should be able to sign and encrypt documents. Customer Need/Problem Since digital signatures and encryption will be heavily used in the government space, many citizens with low or average PC skill will want or have to use digital security technologies. Therefore, they have to be very easy to use and well documented. Comment Eng Effort Eng Owner Matthias Huetsch / Lutz Hoeger Product Concept Initial concept: Learn from competing applications User Interaction. Detailed concept needs to be provided by User Experience Team. Functional Specification - MHU->LHO: The more I think about this, the more I conclude that this a meta task requiring 'ease of use' for all signature / encryption functionality that your team is designing for the Writer / Calc / ... teams. Thus, can you please take care of this (e.g. delegate to FL)? LHO->FL: Frank, I agree with Matthias. Please include into the signature specification.
*** Issue 5903 has been marked as a duplicate of this issue. ***
I just read this enews http://news.com.com/2100-1012_3-5089536.html Adobe and Microsoft are now battling for new standard in e-forms. Both companies are pushing their own propritiery products. Microsoft has XDocs (now its Infopath) and Adobe has PDF. Both has now support for XML and digital signature. Is XML will play a big role on implementation of digital signature on OpenOffice?
added keyword Q-PCD
.
TL->GT: OS said this one was for you.
according to the announcement on releases (http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue will be re-targeted to OOo Later.
Hi Frank, This is an 'ease of use' meta task for signature / encryption functionality that *will* be implemented for OOo 2.0, and thus needs to be taken care as well. I'm thus re-prioritizing (P5 to P3) and re-targeting ('OOo Later' to 'OOo 2.0') this task. Also, I'm not sure that GT is the correct owner (and all those '.' comments don't help either) so I'm reassigning to you. Matthias
FL->EM: Now ready for translation
sent out for external review; planned done July 7
Just CC'ing myself and whats the status for this issue ? Is it really target OOo2.0 ?
rev done, Changes coming via mail.
Please find the specification here: http://specs.openoffice.org/appwide/security/Electronic_Signatures_and_Security.sxw Status is still draft, because we need approval of FST from QA.
According to FST the spec has been finally approved by the i-team, and the CWS is already being integrated. So QA has already verified the feature implementation being compliance with the specification. LHO->FL: FIXED/VERIFIED?
FL: Changed status to fixed.
FL: Verified.
Seen good in src680 m63.
*** Issue 10407 has been marked as a duplicate of this issue. ***