summaryrefslogtreecommitdiff
path: root/tests/example_filesystems/v1.1-reverse-plaintextnames/.gocryptfs.reverse.conf
diff options
context:
space:
mode:
authorJakob Unterwurzacher2017-10-01 13:50:25 +0200
committerJakob Unterwurzacher2017-10-01 13:50:25 +0200
commit4da245c69d7994efec75e1deaef56a03020d39db (patch)
treef9d429bd039774f4ecd06afb18844ece5a4d5bb4 /tests/example_filesystems/v1.1-reverse-plaintextnames/.gocryptfs.reverse.conf
parent0072a96f20c99bf386d8e3f63741def5a3945018 (diff)
fusefrontend_reverse: fix 176-byte names
A file with a name of exactly 176 bytes length caused this error: ls: cannot access ./tmp/dsg/sXSGJLTuZuW1FarwIkJs0w/b6mGjdxIRpaeanTo0rbh0A/QjMRrQZC_4WLhmHI1UOBcA/gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY: No such file or directory ls: cannot access ./tmp/dsg/sXSGJLTuZuW1FarwIkJs0w/b6mGjdxIRpaeanTo0rbh0A/QjMRrQZC_4WLhmHI1UOBcA/gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY.name: No such file or directory -????????? ? ? ? ? ? gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY -????????? ? ? ? ? ? gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY.name Root cause was a wrong shortNameMax constant that failed to account for the obligatory padding byte. Fix the constant and also expand the TestLongnameStat test case to test ALL file name lengths from 1-255 bytes. Fixes https://github.com/rfjakob/gocryptfs/issues/143 .
Diffstat (limited to 'tests/example_filesystems/v1.1-reverse-plaintextnames/.gocryptfs.reverse.conf')
0 files changed, 0 insertions, 0 deletions