File path validation during file transfer - too strict? #190
Unanswered
jenstopp
asked this question in
Design Proposals
Replies: 2 comments
|
IMHO, this behavior makes sense from a security standpoint. It is not advisable to allow the dutagent to access arbitrary files without client-side verification. Verifying that the file appears in the dutctl command line ensures that the client user consents to providing access to the file. |
0 replies
|
#249 had to remove this check because the dutagent configures a fixed destination path to copy to on the client. In my opinion this needs further remedy. Maybe prompt the user to accept the file? It will be removed for now though. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Currently, any file to be transmitted must be named on the dutctl cmdline.
All reactions