Re: Feature Request: Changeset Signing
From: <kfogel_at_collab.net>
Date: 2005-08-29 05:16:09 CEST
Stefano Spinucci <virgo977virgo@yahoo.it> writes:
I don't know what plans Branko was referring to (in the mail from him,
-Karl
-- www.collab.net <> CollabNet | Distributed Development On Demand > > Branko Äibej wrote: > > > > This is on the TODO list, and we have a prettz good idea about how to > > implement it. > > > > -- Brane > > > > Phillip Susi wrote: > > > >> I'd like to suggest a feature request for future versions of > subversion. > >> > >> When using client certificates to authenticate with the server, it > >> would be nice if you could also have the client digitally sign > change > >> sets that you commit. When the client sends the change set it could > >> just compute an MD5 sum of the change set, sign it using the user's > >> private key, and add it to the commit as a revision property. That > >> way later you can validate the signed hash and be certain who made > the > >> change. In effect, it's a digital signature that you authorized and > >> approved the change. This level of change control is required by > >> certain standard engineering practices that are mandated in certain > >> fields, such as medical devices. > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org > For additional commands, e-mail: users-help@subversion.tigris.org > -- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Mon Aug 29 06:17:27 2005 |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.