You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by russellh <ru...@hmgcc.gsi.gov.uk> on 2012/06/15 09:18:10 UTC
missing sha-1 after svndumptool
Hi all,
We have used svndumptool to change all the externals in our Subversion
repositories during a migration due to a change from http to https on
our system.
We noticed that the new file created by svndumptool is missing all the
sha-1 lines (md5s still in there) that were in the old file however
everything seems to work OK on testing.
Is this an issue or is this something we can ignore?
Cheers,
Russell
The information contained in this message (and any attachments) may
be confidential and is intended for the sole use of the named addressee.
Access, copying, alteration or re-use of the e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient please advise the sender immediately by returning the e-mail
and deleting it from your system.
This information may be exempt from disclosure under Freedom Of Information
Act 2000 and may be subject to exemption under other UK information
legislation. Refer disclosure requests to the Information Officer.
The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless Worldwide in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes.
Re: missing sha-1 after svndumptool
Posted by Stephen Butler <sb...@elego.de>.
On Jun 15, 2012, at 12:18 , Stephen Butler wrote:
>
> On Jun 15, 2012, at 9:18 , russellh wrote:
>
>> Hi all,
>>
>> We have used svndumptool to change all the externals in our Subversion repositories during a migration due to a change from http to https on our system.
>>
>> We noticed that the new file created by svndumptool is missing all the sha-1 lines (md5s still in there) that were in the old file however everything seems to work OK on testing.
>>
>> Is this an issue or is this something we can ignore?
>>
>> Cheers,
>>
>> Russell
>
> Subversion's 'svnadmin load' command checks file content against MD5
> checksums. For backward compatibility, neither MD5 nor SHA1 is required.
>
> The 'svnadmin dump' command will write SHA1 checksums, but 'svnadmin
> load' ignores them when parsing a dump file. For historical reasons,
> svndumpfilter reuses the svnadmin dump-parsing code, so it drops SHA1s
> too.
Whoops, the preceding sentence is incorrect: svndumpfilter actually preserves
SHA1 data.
Steve
>
> Note that svndumptool is an independent project. I see in their TODO.txt
> "Add support for sha1?". They're probably waiting for Subversion to start
> using the SHA1s.
>
> So there's no short-term issue for you to worry about, but I suppose it's about
> time we (Subversion) stopped dropping SHA1s when parsing dump files. As
> it happens, I'm changing the dump parsing code right now, so I'll add that to
> my list.
>
> Steve
>
> --
> Stephen Butler
> elego Software Solutions GmbH
> http://www.elego.de
>
--
Stephen Butler
Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 / Building 12
13355 Berlin, Germany
tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elego.de
Geschäftsführer: Olaf Wagner, Michael Diers
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Charlottenburg HRB 77719
Re: missing sha-1 after svndumptool
Posted by russellh <ru...@hmgcc.gsi.gov.uk>.
Thanks Steve,
That's really useful. In that case we shall carry on with our migration
using svndumptool.
We are aware it's a third party application, but since it affects our
Subversion dump files we thought that you guys would be better placed to
answer whether this would cause an issue with usage of the output dump
files.
It sounds like the MD5 check sums are enough so that's good.
Thanks again for the swift response!
Russell
On 15/06/2012 11:18, Stephen Butler wrote:
>
> On Jun 15, 2012, at 9:18 , russellh wrote:
>
>> Hi all,
>>
>> We have used svndumptool to change all the externals in our Subversion repositories during a migration due to a change from http to https on our system.
>>
>> We noticed that the new file created by svndumptool is missing all the sha-1 lines (md5s still in there) that were in the old file however everything seems to work OK on testing.
>>
>> Is this an issue or is this something we can ignore?
>>
>> Cheers,
>>
>> Russell
>
> Subversion's 'svnadmin load' command checks file content against MD5
> checksums. For backward compatibility, neither MD5 nor SHA1 is required.
>
> The 'svnadmin dump' command will write SHA1 checksums, but 'svnadmin
> load' ignores them when parsing a dump file. For historical reasons,
> svndumpfilter reuses the svnadmin dump-parsing code, so it drops SHA1s
> too.
>
> Note that svndumptool is an independent project. I see in their TODO.txt
> "Add support for sha1?". They're probably waiting for Subversion to start
> using the SHA1s.
>
> So there's no short-term issue for you to worry about, but I suppose it's about
> time we (Subversion) stopped dropping SHA1s when parsing dump files. As
> it happens, I'm changing the dump parsing code right now, so I'll add that to
> my list.
>
> Steve
>
> --
> Stephen Butler
> elego Software Solutions GmbH
> http://www.elego.de
>
The information contained in this message (and any attachments) may
be confidential and is intended for the sole use of the named addressee.
Access, copying, alteration or re-use of the e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient please advise the sender immediately by returning the e-mail
and deleting it from your system.
This information may be exempt from disclosure under Freedom Of Information
Act 2000 and may be subject to exemption under other UK information
legislation. Refer disclosure requests to the Information Officer.
The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless Worldwide in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free.
Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes.
Re: missing sha-1 after svndumptool
Posted by Stephen Butler <sb...@elego.de>.
On Jun 15, 2012, at 9:18 , russellh wrote:
> Hi all,
>
> We have used svndumptool to change all the externals in our Subversion repositories during a migration due to a change from http to https on our system.
>
> We noticed that the new file created by svndumptool is missing all the sha-1 lines (md5s still in there) that were in the old file however everything seems to work OK on testing.
>
> Is this an issue or is this something we can ignore?
>
> Cheers,
>
> Russell
Subversion's 'svnadmin load' command checks file content against MD5
checksums. For backward compatibility, neither MD5 nor SHA1 is required.
The 'svnadmin dump' command will write SHA1 checksums, but 'svnadmin
load' ignores them when parsing a dump file. For historical reasons,
svndumpfilter reuses the svnadmin dump-parsing code, so it drops SHA1s
too.
Note that svndumptool is an independent project. I see in their TODO.txt
"Add support for sha1?". They're probably waiting for Subversion to start
using the SHA1s.
So there's no short-term issue for you to worry about, but I suppose it's about
time we (Subversion) stopped dropping SHA1s when parsing dump files. As
it happens, I'm changing the dump parsing code right now, so I'll add that to
my list.
Steve
--
Stephen Butler
elego Software Solutions GmbH
http://www.elego.de