Here are this month's most popular ideas about Archive Manager . New to Brainstorm? Learn how it works !
Something should be done about executables in Archives. It's a security risk.
Written by Chocwise the 6 Nov 09 at 15:51.
New
Some archive types, tar.gz for example, can contain files with preset executable bit.
That means someone could give you an archive with stuff like info.odf in it, wich is actually no Oo.org-Document but a binary malware with the executable bit preset.
If you aren't paying attention to the actual icon or the mime type, you could be tricked into executing the malware.
Solution #2:
Archive Manager should have a pre-selected option to remove all executable bits
Written by
Chocwise the 6 Nov 09 at 15:56.
Before unpacking archives, Archive Manager should ask the User if executable bits should be stripped off of included files.
That Opion should be pre-checked, so that one can not accidentally forget about it.
Before unpacking archives, Archive Manager should ask the User if executable bits should be stripped off of included files.
That Opion should be pre-checked, so that one can not accidentally forget about it.
Solution #3:
Add new Nautilus extension and change a default behaviour.
Written by
Lachu the 7 Nov 09 at 18:55.
Nautilus should have unpack/install software option and all other unpack options should drop executable bit.
It very intuitive for new users. If I have downloaded software, I wanna install it. In other cases I only need to unpack files.
It will be non-intuitive for admins, which will make backup of whole system(with executable too).
Changes will be done only in GUI. Console tools shouldn't been touched.
Nautilus should have unpack/install software option and all other unpack options should drop executable bit.
It very intuitive for new users. If I have downloaded software, I wanna install it. In other cases I only need to unpack files.
It will be non-intuitive for admins, which will make backup of whole system(with executable too).
Changes will be done only in GUI. Console tools shouldn't been touched.
Solution #4:
Solution #1 + #!2
Written by
sybiam the 12 Nov 09 at 08:28.
I'm not for "pre-selected option to remove all executable bits". Honestly by default, the extract manager should extract file like it always did. Keep the old behaviour but warn the user before sounds good to me.
The user should be warn about executables files. It should list all executable files. Then give you the choice.
a) continue with default behaviour
b) continue with removed executable bits
c) do not warn me again and save the current selected behaviour.
But I do find it usefull to extract without executable bits...Sometimes people on windows archive files but on windows everything is executable. This is not exactly a problem.
on the list of file. I'd also see a "checkbox" allowing only certain files to be executables.
I'm not for "pre-selected option to remove all executable bits". Honestly by default, the extract manager should extract file like it always did. Keep the old behaviour but warn the user before sounds good to me.
The user should be warn about executables files. It should list all executable files. Then give you the choice.
a) continue with default behaviour
b) continue with removed executable bits
c) do not warn me again and save the current selected behaviour.
But I do find it usefull to extract without executable bits...Sometimes people on windows archive files but on windows everything is executable. This is not exactly a problem.
on the list of file. I'd also see a "checkbox" allowing only certain files to be executables.