Frank Filz has uploaded this change for review.
Clean up UTF-8 checking in preparation for config option
UTF-8 validation of path components will become optional with a
subsequent patch.
Symlink values MUST NOT be validated.
Compound tags should only be checked for valid UTF-8, there is no
reason to not allow "." and ".." strings or '/' characters.
At the momenent we don't do ANY UTF-8 validation for the strings
that RFC 7530 says MUST be valid UTF-8.
Change-Id: Ie6d1fbb89148168715b95b3d907e37f852a6064e
Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
---
M src/Protocols/NFS/nfs4_Compound.c
M src/Protocols/NFS/nfs4_op_create.c
M src/Protocols/NFS/nfs4_op_link.c
M src/Protocols/NFS/nfs4_op_lookup.c
M src/Protocols/NFS/nfs4_op_open.c
M src/Protocols/NFS/nfs4_op_remove.c
M src/Protocols/NFS/nfs4_op_rename.c
M src/Protocols/NFS/nfs4_op_secinfo.c
M src/Protocols/NFS/nfs_proto_tools.c
M src/include/nfs_proto_tools.h
10 files changed, 41 insertions(+), 30 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/27/475927/1
To view, visit change 475927. To unsubscribe, or for help writing mail filters, visit settings.