an option to check that commands are signed with a trusted GPG key before execut... #11

New Issue

2023-10-16T23:31:38+01:00

github-actions[bot] commented

2023-10-16 23:31:38 +01:00

(Migrated from github.com)

This would allow the user to run this on a filesystem containing a mix of trusted and

untrusted files (e.g. tar -zxf untrusted-downloaded-file.tar.gz is dangerous). In order to

prevent replay attacks, the signed data should include things like the path to the

symlink-command (otherwise re-using that signed symlink-command in another location with

different files could be used to change the semantics of the command), and/or the inputs

the command itself and the hash of the input files

2043072a87/fs.py (L209)


    FUSE(FilterFS(source, cache), mountpoint, nothreads=True, foreground=True, direct_io = True)

if __name__ == '__main__':
    main(sys.argv[1], sys.argv[2], sys.argv[3])

# TODO: an option to check that commands are signed with a trusted GPG key before executing them
#       This would allow the user to run this on a filesystem containing a mix of trusted and
#       untrusted files (e.g. tar -zxf untrusted-downloaded-file.tar.gz is dangerous). In order to
#       prevent replay attacks, the signed data should include things like the path to the
#       symlink-command (otherwise re-using that signed symlink-command in another location with
#       different files could be used to change the semantics of the command), and/or the inputs
#       (the command itself and the hash of the input files)

This would allow the user to run this on a filesystem containing a mix of trusted and untrusted files \(e\.g\. tar \-zxf untrusted\-downloaded\-file\.tar\.gz is dangerous\)\. In order to prevent replay attacks, the signed data should include things like the path to the symlink\-command \(otherwise re\-using that signed symlink\-command in another location with different files could be used to change the semantics of the command\), and/or the inputs \(the command itself and the hash of the input files\) https://api.github.com/SuzanneSoy/filesystem-fuse/blob/2043072a87447a23ee61d8ffcaacb438159f5c0b/fs.py#L209 ```python FUSE(FilterFS(source, cache), mountpoint, nothreads=True, foreground=True, direct_io = True) if __name__ == '__main__': main(sys.argv[1], sys.argv[2], sys.argv[3]) # TODO: an option to check that commands are signed with a trusted GPG key before executing them # This would allow the user to run this on a filesystem containing a mix of trusted and # untrusted files (e.g. tar -zxf untrusted-downloaded-file.tar.gz is dangerous). In order to # prevent replay attacks, the signed data should include things like the path to the # symlink-command (otherwise re-using that signed symlink-command in another location with # different files could be used to change the semantics of the command), and/or the inputs # (the command itself and the hash of the input files) ```

Sign in to join this conversation.