To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92645


User cmc changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'aziem,cmc,hbrinkm,jeongky|'aziem,cmc,hbrinkm,jeongky
                        |u,kpalagin'               |u,kohei,kpalagin'
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Fri Jun 26 10:11:22 +0000 
2009 -------
cmc->dr/hbrinkm/kohei: Attached is an implementation of the MS XML decryption
mechanism. I've only done the decryption work and hard-coded the password to the
classic Excel default "VelvetSweatshop", which means that applied and
out-of-the-box it's able to open "protected" documents like 
http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/ISA_PNPID_List.xlsx

but someone needs to extend it to query/accept used-entered passwords, and/or
break it up, move it around, check for failures at the various intermediate
steps return values

openssl is in the "vanilla" build-tree, so I've implemented it using that, so it
should be ok from that sense.

FWIW, one quirk of their "bundle it into a OLE2 package and encrypt the whole
zip as a stream in that package" mechanism is that it won't be possible to
detect the file type until *after* its bee decrypted

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to