You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Joshua Slive (JIRA)" <ji...@apache.org> on 2006/05/15 19:17:08 UTC
[jira] Closed: (INFRA-798) Exclude *.md5 from mirroring
[ http://issues.apache.org/jira/browse/INFRA-798?page=all ]
Joshua Slive closed INFRA-798:
------------------------------
Resolution: Fixed
Ok. This has been added to our config. We'll see if it causes any problems.
(Incidentally, there seem to be a conflict on ajax about what was the live rsyncd.conf. I believe it was the one in /etc, not the one in /usr/local/etc. I've renamed the latter to avoid confusion.)
> Exclude *.md5 from mirroring
> ----------------------------
>
> Key: INFRA-798
> URL: http://issues.apache.org/jira/browse/INFRA-798
> Project: Infrastructure
> Type: Task
> Security: public(Regular issues)
> Components: Mirrors
> Reporter: Henri Yandell
>
> This has come up a few times in conversation - that checking the md5 on the mirror against the file downloaded from the mirror does not add anything security-wise. Instead the user should be checking the md5 on the main apache site.
> To that end - the suggestion that has come up each time is to exclude the md5's from the mirroring.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Closed: (INFRA-798) Exclude *.md5 from mirroring
Posted by "Henk P. Penning" <he...@apache.org>.
On Mon, 15 May 2006, Joshua Slive (JIRA) wrote:
> Date: Mon, 15 May 2006 17:17:08 +0000 (GMT+00:00)
> From: "Joshua Slive (JIRA)" <ji...@apache.org>
> To: infrastructure-issues@apache.org
> Subject: [jira] Closed: (INFRA-798) Exclude *.md5 from mirroring
>
> [ http://issues.apache.org/jira/browse/INFRA-798?page=all ]
>
> Joshua Slive closed INFRA-798:
> ------------------------------
>
> Resolution: Fixed
>
> Ok. This has been added to our config. We'll see if it causes any problems.
>
> (Incidentally, there seem to be a conflict on ajax about what was the
> live rsyncd.conf. I believe it was the one in /etc, not the one in
> /usr/local/etc. I've renamed the latter to avoid confusion.)
Eh, the rsyncd.conf says
# rsyncd.conf
# DO NOT EDIT /etc/rsync.conf
# ORIGINAL IN /usr/local/etc/rsync.conf
Sometimes '/etc/rsync.conf' gets lost in upgrades etc.
The idea was to have an 'original' in '/usr/local/etc/rsync.conf'
and a 'working copy' in '/etc/rsync.conf'.
HPP
---------------------------------------------------------------- _
Henk P. Penning, Computer Systems Group R Uithof CGN-A232 _/ \_
Dept of Computer Science, Utrecht University T +31 30 253 4106 / \_/ \
Padualaan 14, 3584CH Utrecht, the Netherlands F +31 30 251 3791 \_/ \_/
http://www.cs.uu.nl/~henkp/ M penning@cs.uu.nl \_/