Issue 55821 - Encrypted & signed document doesn't open
Summary: Encrypted & signed document doesn't open
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P2 Trivial
Target Milestone: ---
Assignee: frank
QA Contact: issues@api
URL:
Keywords: oooqa
: 56355 57249 61799 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-10-12 14:29 UTC by kravietz
Modified: 2013-02-24 21:07 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
This test signed & encrypted document doesn't open (pass "abc123") (12.88 KB, application/vnd.sun.xml.calc)
2005-10-12 14:31 UTC, kravietz
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kravietz 2005-10-12 14:29:57 UTC
In latest OO 2-beta it's impossible to open a spreadsheet that has been saved
with password (encrypted) and then digitally signed in ODS format.

I created a spreadsheet and saved it with password. It opens OK.

I created another ODS and digitally signed it with a smartcard under Windows (no
password). It opens OK.

I created yet another spreadsheet and saved it with password. I then saved it
with password, then again digitally signed and this time it doesn't open. I
always get "Read-error. Invalid password" message when opening the document. The
password is correct and this has been repeated several times.

All this happens under Windows XP.

You can test this behaviour using these files created as described above. The
password is always "abc123".


      http://67.15.157.7/~kabardia/echelon/OO2/Encrypted%20test.ods
      http://67.15.157.7/~kabardia/echelon/OO2/Signed%20test.ods
      http://67.15.157.7/~kabardia/echelon/OO2/Encrypted%20signed%20test.ods



The last one doesn't open.
Comment 1 kravietz 2005-10-12 14:31:02 UTC
Created attachment 30344 [details]
This test signed & encrypted document doesn't open (pass "abc123")
Comment 2 stephan.wunderlich 2005-10-12 16:18:18 UTC
sw->mt: after entering the given password "abc123" I get the message that the
password is wrong and the document isn't opened ... please have a look at this
Comment 3 flibby05 2005-10-13 10:42:52 UTC
sw, mt:
is it possible to target this issue to 2.0.1?
This bug would definitely lock away user's documents..
Comment 4 malte_timmermann 2005-10-13 11:19:59 UTC
mt->mv: Happens within xLoadable->load() call, signature component is not involved.
Wrong Password Exception, seems you try to open the signature stream encrypted,
but it isn't...
Comment 5 mikhail.voytenko 2005-10-13 15:02:45 UTC
The problem is much more dangerous, it does not happen on loading but on
signing. In case of signing an encrypted document it's encryption information is
errorneusly exchanged, thus the document can not be successfuly decrypted any more.
Fixed.
Comment 6 mikhail.voytenko 2005-10-14 10:11:01 UTC
.
Comment 7 mikhail.voytenko 2005-10-14 13:06:17 UTC
Pawel Krawczyk wrote:
>Does this mean the document cannot be recovered in any way? Is the
>keying info preserved somewhere so that it could be recovered manually?

No there is no way to get this info any more, the only way to open the document
is a brutal force hacking ( means trying to get acceptable encryption
initialization info ). I would say it needs even more resources than to hack a
correct encrypted OOo document without knowing the password.

>BTW the same bug was reported as issue 55263.
Then the issue 55263 can be closed as a duplicate to this one.
Comment 8 mikhail.voytenko 2005-10-17 11:01:01 UTC
Please verify the issue.

re-open issue and reassign to fst@openoffice.org
Comment 9 mikhail.voytenko 2005-10-17 11:01:29 UTC
reassign to fst@openoffice.org
Comment 10 mikhail.voytenko 2005-10-17 11:02:07 UTC
reset resolution to FIXED
Comment 11 frank 2005-10-20 14:08:06 UTC
found fixed on cws fwk24 using Linux, Solaris and Windows build
Comment 12 lohmaier 2005-11-05 18:45:31 UTC
*** Issue 56355 has been marked as a duplicate of this issue. ***
Comment 13 frank 2005-11-22 10:06:50 UTC
found fixed on master m142 using Linux, Solaris and Windows build
Comment 14 frank 2006-02-09 09:07:10 UTC
*** Issue 61799 has been marked as a duplicate of this issue. ***
Comment 15 jbf.faure 2008-01-01 16:17:58 UTC
It does'nt work for me with OOo 2.3.1 and OOo-Dev_SRC680_m239 under Kubuntu 6.06.
Please reopen this issue.
I went to this issue from #57249 which seems to be a duplicate of this one.
Comment 16 andreschnabel 2008-07-15 22:09:32 UTC
*** Issue 57249 has been marked as a duplicate of this issue. ***
Comment 17 andreschnabel 2008-07-15 22:11:31 UTC
this works fine for me using OOo 2.3, 2.4.1 and 3.0beta2 on Windows

I cannot get a working certificate on linux / OOo, so I cannot test there.

jbfaure: please reopen, if you find the issue still exists in a current version 
Comment 18 lohmaier 2008-07-15 22:28:16 UTC
works on linux as well (2.4.1) (although I had to start soffice.bin directly to
be able to use my certificates, otherwise there were no certificates listed).

A little annoying though: When another document is already open, and I open the
password-protected (and signed) document via the recent document list in OOo,
the password-prompt appears behind the new window (that at this time only
consists of a grey background and the titlebar). But the document can be opened
after entering the password.