[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [buildd] Implications of DSA-1571-1



Might as well collect an up-to-date listing for all the buildds. I'm
hoping we'll have the opportunity to update keys at buildd.d.o. So I'd
like to update all the questions we normally get asked.

The question is, should we maintain this on a wiki where it can be
updated? We've potentially got 25 buildds if all of them were up and
running. I can keep that in a spreadsheet, but it'll bit rot as soon as
something changes and I don't notice. (Look a shiny thing, I must chase
it. :)

The only downside I see is spam harvesting and frankly I've got a nice
procmail filter that keeps spam from making it to my buildds (buildd
mail only knows six messages, everything else must be spam). If I was
really clever, I could probably drop such messages earlier. Hmmmm.

What other questions should we ask/track?

Thanks,

Stephen


builddname: buildd_m68k-foo
hostname: foo.debian.org
dynamic/static ip: static
ssh connection info: ssh -p2145 foo.debian.org
buildd email: buildd@foo.debian.org
buildd admin(s): John Doe <bar@debian.org>
local admin: Jane Baz <baz@foobar.com>
configured suites: experimental, unstable, testing, testing-security

host key: 
ssh-rsa blahblahblah root@foo

buildd ssh key: 
ssh-rsa blahblahblah buildd@foo

kernel: 2.6.25-2
distro: etch-m68k
has patched ssl and ssh (yes,no,n/a): yes

-- 
Stephen R. Marenka     If life's not fun, you're not doing it right!
<stephen@marenka.net>

Attachment: signature.asc
Description: Digital signature


Reply to: