https://bugs.documentfoundation.org/show_bug.cgi?id=42647
--- Comment #7 from william.tambell...@gmail.com ---
+1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=42647
gmoll...@us.es changed:
What|Removed |Added
CC||gmoll...@us.es
--- Comment #6
https://bugs.documentfoundation.org/show_bug.cgi?id=42647
Yousuf Philips (jay) changed:
What|Removed |Added
Blocks|
https://bugs.documentfoundation.org/show_bug.cgi?id=42647
Xisco Faulí changed:
What|Removed |Added
Status|ASSIGNED|NEW
--
https://bugs.documentfoundation.org/show_bug.cgi?id=42647
--- Comment #5 from Thibaut Barrère ---
I tried to use soffice to automate conversion of XLSX encrypted files in a
production environment, and ended up finding this ticket.
If we were to follow twelve-factor
https://bugs.documentfoundation.org/show_bug.cgi?id=42647
Mani man...@gmail.com changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4
https://bugs.freedesktop.org/show_bug.cgi?id=42647
sasha.libreoff...@gmail.com changed:
What|Removed |Added
CC||sasha.libreoff...@gmail.com
https://bugs.freedesktop.org/show_bug.cgi?id=42647
--- Comment #2 from Battery Staple correct.ho...@aol.com 2012-04-19 07:35:05
PDT ---
I've described a scenario where it makes sense to supply the password in
plaintext. Plus I've asked for keyfile support, so what's your problem with
that?
--
https://bugs.freedesktop.org/show_bug.cgi?id=42647
sasha.libreoff...@gmail.com changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0