Documentation update - SMAFT

1 votes

I'd like to see some more thorough documentation in how the SMAFT process works, how permissions for files are added, especially in Windows. For instance, I recently discovered that due to the use of the <drive:>\OpConTemp folder in Windows being the first directory a SMAFT file is written to before making it to the destination, it inherits the permissions of that folder instead of the actual destination folder. I'm curious if something like this happens in UNIX as well?

I'm also interested if path traversal is required for sub-folders in Windows. For instance, if I'm transferring a file from C:\Path\Path2\file.txt, do we require permissions to C:\Path, or just C:\Path\Path2?

Documenting exactly how each step of the SMAFT process works would be extremely beneficial in troubleshooting when there are issues.

Collecting community feedback Documentation Suggested by: Hidden identity Upvoted: 27 Jan, '21 Comments: 0

Comments: 0