FTP frontend should avoid caching plaintext of uploads #1083
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1083
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The SFTP frontend was changed to avoid using a cleartext temporary file for the contents of files opened for writing (see [EncryptedTemporaryFile in sftpd.py]source:src/allmydata/frontends/sftpd.py?rev=4478#L294). A similar change should be made to the FTP frontend.
Perhaps
EncryptedTemporaryFile
should be moved to [fileutil.py]source:/src/allmydata/util/fileutil.py so that it can be used by both SFTP and FTP.Note that
EncryptedTemporaryFile
is not tested directly, only via the SFTP tests. It probably should be tested directly.The FTP frontend unfortunately has no tests (#512). On the other hand,
EncryptedTemporaryFile
is indirectly tested by the SFTP tests.Perhaps this should be bumped from v1.7.1 to v1.8.0 simply due to it being a nice new feature instead of a bug fix, clean-up, unfinished-business, etc.?
Oh, it is sort of a bug-fix (potential security problem), clean-up (unify SFTP and FTP backends), and unfinished-business (SFTP got this feature in 1.7.0). So disregard comment:77998. :-)
The current patch seems to have caused a regression in SFTP that results in the test_openFile_write test hanging (probably something simple, but I haven't had time to track it down). So I wouldn't object to this being bumped to 1.8. Whether we'll fit it into 1.7.1 depends on how much the schedule slips :-)
Replying to davidsarah:
I was mistaken; this was caused by sftp-no-trunc-files-opened-with-append.dpatch, not by this patch.
Attachment make-ftp-use-encrypted-temporary-file.dpatch (11005 bytes) added
Move EncryptedTemporaryFile from SFTP frontend to allmydata.util.fileutil, and make the FTP frontend also use it (fi xing #1083). Also, docstrings for non-obvious usage restrictions on methods of EncryptedTemporaryFile.
I just reviewed the patch. +1! Thanks, David-Sarah!
Oh, it needs a NEWS snippet. I'll add that myself.
Should we remove the "test-needed" flag?
Replying to zooko:
That would be part of #512, so yes.
committed in changeset:05022dca36780b3b. Thanks!