Return-Path: 
 <dev-return-33231-apmail-subversion-dev-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org
Delivered-To: apmail-subversion-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 413A81759D
	for <apmail-subversion-dev-archive@minotaur.apache.org>;
 Mon,  8 Jun 2015 05:37:07 +0000 (UTC)
Received: (qmail 56248 invoked by uid 500); 8 Jun 2015 05:37:07 -0000
Delivered-To: apmail-subversion-dev-archive@subversion.apache.org
Received: (qmail 56197 invoked by uid 500); 8 Jun 2015 05:37:07 -0000
Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@subversion.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@subversion.apache.org>
List-Post: <mailto:dev@subversion.apache.org>
List-Id: <dev.subversion.apache.org>
Delivered-To: mailing list dev@subversion.apache.org
Delivered-To: moderator for dev@subversion.apache.org
Received: (qmail 97387 invoked by uid 99); 8 Jun 2015 02:19:42 -0000
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.899
X-Spam-Level: **
X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	HTML_MESSAGE=3, SPF_PASS=-0.001] autolearn=disabled
Authentication-Results: spamd4-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:message-id:subject:mime-version:content-type;
        bh=1xfQ1WQM5PkfsabQEmlD8+NsCQognobZoamgmSToNL8=;
        b=HtoDdGI5gNerIy6Oe6C8cq5CU/ZYy7HjoVDnvIOw7VMFU3YPxOcjsh4guW7b7qOvLk
         JMj6K2zxKS5I7eD8kx02kC3WeS0s8ngSZ0L4g7SNMwDV6ZTIXUcTp5Eh4nBNn+XdGStw
         66wGY6opBgRf/KYvurjJMIRTtdFDWuU3SIhTUSusLLR1e3f7TmIEzOQ32kYJK0Z/pxQs
         UdvnQGuIkYiyTdZtcVRQWB4zX9gPJNrXZ2ECYAu+8+sDaa26WF6yjYDk12kF/P2v6V+Z
         peoEhJJalvGTsym1mo4M6HA0YG8Pn6j3w6GrEB7/hsj214jl1j2ue3ivfZa88AnUrktC
         /8xQ==
X-Received: by 10.140.102.172 with SMTP id w41mr154894qge.40.1433729969566;
        Sun, 07 Jun 2015 19:19:29 -0700 (PDT)
X-Google-Web-Client: true
Date: Sun, 7 Jun 2015 19:19:29 -0700 (PDT)
From: Ruchir Arya <ruchirarya@gmail.com>
To: subversion-development@googlegroups.com
Message-Id: <d1707d9d-0a1a-4aa9-b125-77e948b59c0a@googlegroups.com>
Subject: Changeset Signing
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_Part_1716_1693226115.1433729969458"
X-Google-IP: 73.10.1.137

------=_Part_1716_1693226115.1433729969458
Content-Type: multipart/alternative;
	boundary="----=_Part_1717_1745508408.1433729969458"

------=_Part_1717_1745508408.1433729969458
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello everybody,

I am new to SVN development. I have a question. Why is there no 
implementation of changeset signing in subversion? Suppose if the 
root/admin (who maintains repository) is not trustworthy, then there is a 
problem. Is there any future possibility to implement digital signing of 
changeset to achieve integrity and non repudiation? My focus is to 
implement some of the security related features in svn.

Regards,
Ruchir Arya

------=_Part_1717_1745508408.1433729969458
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div dir="ltr">Hello everybody,<div><br></div><div>I am new to SVN development. I have a question. Why is there no implementation of changeset signing in subversion? Suppose if the root/admin (who maintains repository) is not trustworthy, then there is a problem. Is there any future possibility to implement digital signing of changeset to achieve integrity and non repudiation? My focus is to implement some of the security related features in svn.<br></div><div><br></div><div>Regards,</div><div>Ruchir Arya</div></div>
------=_Part_1717_1745508408.1433729969458--

------=_Part_1716_1693226115.1433729969458--