Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upTrusted image conversion should explicitly label trusted output and preserve original filename #2437
Comments
andrewdavidwong
added
bug
C: other
labels
Nov 15, 2016
andrewdavidwong
added this to the Release 3.2 milestone
Nov 15, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Nov 15, 2016
Member
Actually, there is a difference in workflow: the PDF converter moves the original file to an "Untrusted " folder, whereas the image converter leaves both in place, and leaves it to the user to deal with them.
It seems more likely that users will want to keep the original PDF, rather than the original image, because of the fact that there is more functionality in the original.
I like having the file marked "untrusted", and this is implicit in the PDF case because of the folder name.
|
Actually, there is a difference in workflow: the PDF converter moves the original file to an "Untrusted " folder, whereas the image converter leaves both in place, and leaves it to the user to deal with them. |
andrewdavidwong commentedNov 15, 2016
Qubes OS version (e.g.,
R3.1):R3.2
There are (at least) three reasons in favor of this change:
On 2016-11-15 06:00, '091823'04918'032948'1093248018243 wrote:
Related issues:
#1995