monotone - Bugs: bug #16790, SSL for confidentiality (and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #16790: SSL for confidentiality (and perhaps authentication)
Submitter: | None | ||
Submitted: | Thu 08 Jun 2006 08:55:01 PM UTC | ||
Category: | cryptography | Severity: | 3 - Normal |
Item Group: | feature request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: | monotone 0.26 (base revision: 4342565107f26ceda955b66c66b5b7ec152f314e)
|
Jump to the original submission
Mon 19 Jun 2006 08:44:58 AM UTC, comment #10: |
Jack Lloyd <randombit> |
Mon 19 Jun 2006 08:37:04 AM UTC, comment #9:
|
Jack Lloyd <randombit> |
Sun 11 Jun 2006 07:52:31 PM UTC, comment #8: Oh, and re: the bug title -- you have to use the same system for both confidentiality and authentication, because otherwise your confidentiality is open to MITM attacks.
|
Nathaniel Smith <njs> |
Sun 11 Jun 2006 07:48:52 PM UTC, comment #7: In principle I think we'd be happy to use SSL at the channel layer. Having our own crypto there gives me the heebie-jeebies, too. There are some reasons why this isn't what we did from the start, though:
|
Nathaniel Smith <njs> |
Fri 09 Jun 2006 01:02:08 AM UTC, comment #6:
|
Anonymous |
Fri 09 Jun 2006 12:35:21 AM UTC, comment #5: Yeah, SSH is mostly for private use. You can scale it up a bit if you put entries in your .ssh/authorized_keys file with a command restriction (similar to http://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH) but it's not terribly satisfying, I'll admit.
|
graydon hoare <graydon> |
Fri 09 Jun 2006 12:33:14 AM UTC, comment #4: (I have a feeling my first questions can be answered by reading the hook documentation. I will do so tonight) |
Anonymous |
Fri 09 Jun 2006 12:17:15 AM UTC, comment #3:
|
Anonymous |
Thu 08 Jun 2006 09:30:55 PM UTC, comment #2: I should say "the soon-to-be-released 0.27", since there's no such release yet. |
graydon hoare <graydon> |
Thu 08 Jun 2006 09:30:12 PM UTC, comment #1: 0.27 can speak over ssh, with an ssh:// URI form as the "host" parameter of push/pull/sync. It is also extensible in lua scripts to use any other full duplex channel you can run as a subprocess. Good enough?
|
graydon hoare <graydon> |
Thu 08 Jun 2006 08:55:01 PM UTC, original submission:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-f8d8.
Corresponding source code
(Finally bothered to get an account)