Bug 83231 - VIEWING: Thumbnails show content of password protected files
Summary: VIEWING: Thumbnails show content of password protected files
Status: RESOLVED DUPLICATE of bug 80755
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-29 08:20 UTC by AME
Modified: 2014-08-29 08:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Screenshot (224.24 KB, image/jpeg)
2014-08-29 08:20 UTC, AME 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description AME 2014-08-29 08:20:55 UTC 
Created attachment 105414 [details]
Screenshot

Problem description: 
Thumbnails show content of password protected files.

Steps to reproduce:
1. Open Libre Office (not a specific application)

Current behavior:
The large thumbnails of recent documents show the content of password protected files. These are large enough to read.
This means anyone can see the content.
Correcting this bug will be locking the stable door after the horse has bolted - even when you fix this bug anyone with an old version of LibreOffice will be able to read part of any password protected office file

Expected behavior:
You should not be able to read any part of a password protected file without entering the password.
              
Operating System: Windows 8
Version: 4.3.0.4 release
Comment 1 Maxim Monastirsky 2014-08-29 08:33:42 UTC 
Hi,

This is fixed for the next stable release (4.3.2).

(In reply to comment #0)
> even when you fix this bug anyone with an old version of
> LibreOffice will be able to read part of any password protected office file
That's simply not true. Thumbnails can be generated only after a file is open, and you can't open password protected file without entering the password first.

*** This bug has been marked as a duplicate of bug 80755 ***