Re: Bad press again...

2005-08-26 Thread martin f krafft
also sprach martin f krafft <[EMAIL PROTECTED]> [2005.08.26.1907 +0200]: > security.debian.org is not a server, it's a DNS A record. It's > a whole lot easier to point that elsewhere in case of problems than > expecting users to make sense of the errors they get when some > servers can't be reached

Re: Bad press again...

2005-08-26 Thread martin f krafft
also sprach tomasz abramowicz <[EMAIL PROTECTED]> [2005.08.26.1836 +0200]: > why arent all redundant security servers included in the sources.list, > or why doesnt it ask at install time to include all backup security servers? > as well as security.debian.org? security.debian.org is not a server,

Re: Bad press again...

2005-08-26 Thread W. Borgert
On Fri, Aug 26, 2005 at 05:36:26PM +0200, martin f krafft wrote: > Heck, we *should* have a responsive and communicative security team. Do we have a security team for stable? I know, that we have a security team for testing consisting of nine DDs and ten non-DDs, but it seems to me, that stable i

Re: Bad press again...

2005-08-26 Thread tomasz abramowicz
martin f krafft wrote: also sprach Timo Veith <[EMAIL PROTECTED]> [2005.08.26.1726 +0200]: either case can be solved by: security1.debian.org in LA and security2.debian.org in NYC and security3.debian.org in berlin :-) Reading Package Lists... Done Building Dependency Tree Reading extended s

Re: Bad press again...

2005-08-26 Thread martin f krafft
also sprach Luis M <[EMAIL PROTECTED]> [2005.08.26.1750 +0200]: > perhaps instead of security2.d.o securyN.d.o it should be done like > the ftp aliases: > > security.us.d.o (or better by location like: security.us.ny.d.o) > security.de.d.o, etc... No matter what they are called, it should be poss

Re: Bad press again...

2005-08-26 Thread Luis M
perhaps instead of security2.d.o securyN.d.o it should be done like the ftp aliases: security.us.d.o (or better by location like: security.us.ny.d.o) security.de.d.o, etc... I guess once GPG signed packages (now in Sid) become a reality, these things can be done more safely. -- )(- Lui

Re: Bad press again...

2005-08-26 Thread martin f krafft
also sprach Timo Veith <[EMAIL PROTECTED]> [2005.08.26.1726 +0200]: > >either case can be solved by: security1.debian.org in LA > >and security2.debian.org in NYC and security3.debian.org in berlin :-) > > Reading Package Lists... Done > Building Dependency Tree > Reading extended state informati

Re: Bad press again...

2005-08-26 Thread Steven Brunasso
Yep, that is bad, even here from LA. [EMAIL PROTECTED] ~]$ dig  security1.debian.org @samosa.debian.org. ; <<>> DiG 9.2.5 <<>> security1.debian.org @samosa.debian.org. ; (1 server found) ;; global options:  printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14151 ;; flag

Re: Bad press again...

2005-08-26 Thread Timo Veith
Alvin Oga schrieb: either case can be solved by: security1.debian.org in LA and security2.debian.org in NYC and security3.debian.org in berlin :-) This is interessting but: Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states...

Re: security hole in sshd in oldstable?

2005-08-26 Thread Gaetano Zappulla
Javier Fernández-Sanguino Peña ha scritto: > That's the most common scenario from my experience, SSH scanning is > all too common these days. yes, that's why this type of bug (disclosure of valids user accounts names to remote users) should be fixed on woody's sshd, imho. -- Gaetano Zappulla

unsubscribe

2005-08-26 Thread Ricardo Alarcón
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 unsubscribe -BEGIN PGP SIGNATURE- Version: PGP 8.1 iQA/AwUBQw7nxhDiE0x8B/8iEQKCRQCg7Ap8dvsP3w1vo+imV544XqK3epcAnidw 7sfYmDfRAzQB+bqfnP55PVJg =ohZN -END PGP SIGNATURE- __ Este mensaje, y en su caso, cualquier fi

Re: [SECURITY] [DSA 787-1] New backup-manager package fixes several vulnerabilities

2005-08-26 Thread mfagiolini
** IW/YNGZ Automated reply ** This is a robot-generated message, please don't reply Nel periodo dal 24/8 al 4/9 sarò fuori sede. Tutte le mail verranno archiviate e avrò cura di rispondere non appena possibile. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Tro