https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6511

--- Comment #4 from Karsten Bräckelmann <[email protected]> 2010-11-06 
15:09:01 UTC ---
(In reply to comment #2)
> Regarding the mirror being broken: I've added [email protected] to the 
> CC
> list in hopes that this can be investigated.

While that's perfectly legit and generally precisely the thing to do with
bugzilla, in this case, he gets a copy on the dev list anyway. :)

> Regarding the exit code 0 situation -- I've reviewed the sa-update code, and I
> see exactly how this situation is occurring.  It's actually by design. 

Ah, good one! I've seen a 404 only with third-party channels so far, single
mirror. That explains this.


> Regarding Daryl and the daryl.dostech.ca mirror -- it's not personal, it's 
> just
> that I can't find any mention of this mirror in the SA documentation or on the
> SA Wiki.  These sorts of things should be more public.  It also doesn't 
> reflect
> well on the Apache Foundation when you have a mirror which appears to be 
> broken
> and maintained by someone who's self-proclaimed "lazy" (which in turn makes 
> the
> visitor wonder, in this circumstance, just how valid that claim is), even if 
> he
> is a chairman.

While I kind of understand that argument, and the mirrors probably could be
documented better...

This is open source, and donated resources in this case. An OSS developer's
*personal* site or blog must not be confused with the project.

> I'm sorry if it sounds like I'm overreacting, but given the situation and the
> circumstances, my first inclination was to assume someone had circumvented one
> of the SA mirrors and induced an HTTP redirect to some "mystery" box that had
> been compromised [...]

Why do you run sa-update with the --nogpg option? With the default of using GPG
there would have been no reason to worry. Skipping that security measure was
your deliberate decision.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to