Discussion:
[Libreoffice-bugs] [Bug 121703] Recuva found image which in document that opened by libreoffice
b***@bugs.documentfoundation.org
2018-11-25 14:38:13 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=121703

--- Comment #2 from fake name <***@gmail.com> ---
apparently i just try a bit more testing...saving also cause image to appear in
recuva result.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-11-25 13:52:45 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=121703

--- Comment #1 from fake name <***@gmail.com> ---
if the 1st step doesnt work try save with password then close it and then open
and scroll through all the image and close it again and continue to step 2...

if you remember me i'm the one with broken english reporting about image read
error before.im using windows 7 32-bit and always libreoffice still...waiting
that fixed version of 6.1 to go into still branch(last time i try portable
version its seem okay and the problem seems to be fixed).
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-12-08 06:18:36 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=121703

--- Comment #3 from fake name <***@gmail.com> ---
tested with a new doc(document doesnt have password) using msword 2007(it
cannot open passworded odt?just simple one time test btw and im not sure about
latest version of msoffice).

the result was image opened/saved in document using msoffice 2007 didnt even
show up in recuva result while document opened/saved in lo, be it have password
or not, show up in recuva result list.

please reply, its been 2 week already since this report was made.tq.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-12-10 17:12:41 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=121703

fake name <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Component|LibreOffice |Writer
Resolution|WONTFIX |---
Status|RESOLVED |REOPENED

--- Comment #5 from fake name <***@gmail.com> ---
(In reply to Timur from comment #4)
I'm not sure if this is about document thumbnail or image itself. I didn't
reproduce saving in clear other drive.
Whatever, LO is not a security but office product.
For dubious user case, unlikely that LO image handling will be changed to
avoid something like this.
So I close as WontFix.
image itself...whenever the image was loaded/saved then you closed the
document, you can find them in recuva list in format of png...im actually fine
if they dont find it in those png format like let just say tmp format and its
unopenable but its in .png format with preview of full image and recoverable,
did you use ssd?trim function might kick in before you could reproduce those...

yes lo not security product...but this seriously make me uneasy considering
msword 2007 didnt trigger this...and i didnt test with 6.1/2 branch yet(those
version come with the new memory image handling right?).

change component to writer since im lazy to test other component...reopened
since you might misunderstand what im trying to say since my english pretty
crappy.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@bugs.documentfoundation.org
2018-12-10 16:13:53 UTC
Permalink
https://bugs.documentfoundation.org/show_bug.cgi?id=121703

Timur <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX

--- Comment #4 from Timur <***@gmail.com> ---
I'm not sure if this is about document thumbnail or image itself. I didn't
reproduce saving in clear other drive.
Whatever, LO is not a security but office product.
For dubious user case, unlikely that LO image handling will be changed to avoid
something like this.
So I close as WontFix.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...