address Nathan Wilcox's concerns about "Tahoe and the browser security model" #366
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#366
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?
[//pipermail/tahoe-dev/2008-February/000404.html On the mailing list] Nathan Wilcox posted some general concerns about how Tahoe's WUI relies on a security model which is different than the one almost everyone thinks of when they think of web browsers and URLs.
It is through such cracks between people's models that security failures slip (according to Ross Anderson's book Security Engineering).
If we could address these concerns, at least by documentation, for Tahoe v1.0 I would feel better.
Milestone 1.0.1 deleted
If you like this bug, you might like #127, #615, and #821.
... and #907.
I wonder what process we would use to close this ticket. Maybe: have Nathan Wilcox sign off on it saying "I am no longer concerned about the impedance mismatch between the Tahoe-LAFS security model and the web security model?". I doubt that this would ever happen (at least not for another 5 or 10 years). So maybe we should try to narrow this ticket. Could we name some specific issues that we could verify whether or not they are still a problem and then close the ticket if they are fixed? Probably not.
Nathan: How about this: write a document for the user explaining the dangers of mixing the web security model with Tahoe-LAFS, and then close this ticket. Here is a "seed" document which you could use as a starter:
source:trunk/docs/known_issues.txt
If that document already conveys your concerns to the user, then please close this ticket. If not, please write a document which does do so, or else post a comment on this ticket explaining what it would take to write such a document, or proposing some other process by which we can make forward progress on this ticket.
Thank you!
I will close this ticket because it has vague criteria. Instead, let's focus on more specific issues. A similar ticket not mentioned above is #1665.