Bug 76592 - Password protection in cloud environment
Summary: Password protection in cloud environment
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-03-25 10:40 UTC by Herve LECLAIR
Modified: 2015-07-18 17:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:

Tiny password-protected ODT file (13.60 KB, application/vnd.oasis.opendocument.text)
2014-11-14 09:02 UTC, Robinson Tryon (qubit)

Note You need to log in before you can comment on or make changes to this bug.
Description Herve LECLAIR 2014-03-25 10:40:48 UTC
I have a writer file which is hosted on Google Docs and is password-protected.

open it on PC A (password required)
open it on PC B; no password required.
[ close file on A]
save it from PC B....
close file on B

...No more password protection on the file!

I noticed this process while working on two PCs through a distant link (TeamViewer).  Same thing happened to me last year as I was working in similar conditions but with machine A being under Linux (Ubuntu 12.?).  I did not have the time to clarify the process by then.
Comment 1 Robinson Tryon (qubit) 2014-11-14 09:02:32 UTC
Created attachment 109451 [details]
Tiny password-protected ODT file
Comment 2 Robinson Tryon (qubit) 2014-11-14 09:06:18 UTC
(In reply to Herve LECLAIR from comment #0)
> I have a writer file which is hosted on Google Docs and is
> password-protected.
> open it on PC A (password required)
> open it on PC B; no password required.

As I understand it, opening files *from within* Google Docs or Google Drive means that the data is stored, unencrypted, within Google's cloud architecture.

> ...No more password protection on the file!

I tried uploading password-protected ODT attachment 109451 [details] to Google Drive. I couldn't open it from within Drive/Google Docs, and didn't get offered a preview.

Herve: How can I reproduce this problem?
(Please change status back to UNCONFIRMED after you provide steps to reproduce)

Status -> NEEDINFO
Comment 3 QA Administrators 2015-06-08 14:28:33 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 4 QA Administrators 2015-07-18 17:27:12 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO

Message generated on: 2015-07-18