I have to agree with Klaus Knopper. This is ridiculous. Just because you
think internalizing the library would
be insecure, all the users are forced to write C wrappers or compile their
own ntfs-3g, which bosth will in effect be WAY LESS SECURE, because of the
very reasons you are trying to avoid:
1) People will inexperiencedly "make it work". They are mostly worse than
you at keeping things secure. You can tell yourself that it wasn't you,
but it was you who made the people fix the problem you created by shipping
a broken ntfs-3g.
2) Homebuild ntfs-3g versions aren't updated with the system, leaving the
system to be vulnerable after fuse's bugs are patched in the repository.
3) Wrappers will tear holes because they cause security checks in ntfs-3g
to be skipped, and they will possibly tear open all the holes you are
also trying to keep shut.
Here is my suid wrapper, just to eliminate any doubt that YOUR
NON-SOLUTION of this bug WILL CREATE SECURITY RISKS for every user:
#include <stdlib.h>
#include <string.h>
int main(int argc, char* argv[]){
char* prog = malloc(strlen(argv[0])+5);
strcpy(prog, argv[0]);
strcat(prog, ".bin");
int uid=geteuid();
setuid(uid);
execvp(prog, argv);
exit(127);
}
I'd bet you can find a security risk there besides the fact that it
eliminates the ntfs-3g security checks and alters the defaults.
PS: I don't have any USB drives in /etc/fstab.
My version of Debian:
deb cdrom:[Debian GNU/Linux 7.3.0 _Wheezy_ - Official amd64 NETINST
Binary-1 20131215-04:55]/ wheezy main
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
