Hmm, who has the password to this these days? It's been changed and I
can no longer access it.


---------- Forwarded message ----------
From: Vesa Kaihlavirta <vegai@iki.fi>
Date: Thu, Dec 22, 2011 at 12:22 PM
Subject: Fwd: [arch-dev-public] Developer/TU key signing
To: Aaron Griffin <aaronmgriffin@gmail.com>


Hi Aaron,

It looks like I have lost my ability to send to arch-dev-public. Could
you add me back there?

--vk


---------- Forwarded message ----------
From: *<arch-dev-public-owner@archlinux.org>
Date: Thu, Dec 22, 2011 at 7:33 PM
Subject: Re: [arch-dev-public] Developer/TU key signing
To: vegai@iki.fi


This list is for ArchLinux Development and is not open for public
comment. If there is an important issue, please reply directly to the
original author or to the general ArchLinux mailing list
(arch-general@archlinux.org).

Write access to this list may be provided in special circumstances,
and may need to be evaluated by the rest of the developers. Please
send an email to aaron@archlinux.org to request write access if you
feel you fit a "special circumstance".



---------- Forwarded message ----------
From:*Vesa Kaihlavirta <vegai@iki.fi>
To:*Public mailing list for Arch Linux development
<arch-dev-public@archlinux.org>
Cc:
Date:*Thu, 22 Dec 2011 19:33:25 +0200
Subject:*Re: [arch-dev-public] Developer/TU key signing
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Fri, Nov 25, 2011 at 3:27 PM, Ionut Biru <ibiru@archlinux.org> wrote:
> Hi,
>
> my arch master key is available [1] with fingerprint 44D4 A033 AC14 0143
> 9273 *97D4 7EFD 567D 4C7E A887.
>
> Every packager please do:
>
> 1) reply this email in the mailing list, include gerolde/sigurd username
> and sign your reply using your gpg key.
> 2) name at least one package you already signed.

vegai@sigurd
vesa@gerolde

go-1:r60.3-2-i686

- --vk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJO82rIAAoJEAl9Yp5DdSC9MukH/jwZlRBBVdBP1esb9GTataHK
oSxpZSJgYz+yLyE+obadq2rkFuteomh/zXJL96wo4XSM3cGLbPz6YpV+kF/YcEtX
j9FC6FDN6+KS1uLzwl9QLnUR25SiEtmLZlFy60JZ7ci9Opc2bG 3irB2Mv9If1zwG
jsDYav8/PKVtlM+F46flLbYaC6lpQcN0BueiOimsYuEOsMh/eS39kb7nDgi7Xi2M
Zl95Vudo6gJZbvoviuzLuq/ByB7Yoie+RMgUqrSEPNsC2iOE5TXidsGoajf0CeAK
9t8zSh5vMGVbXnc39ro68WT8PULkvS4aeoCBF2uWBR+xTEQX0U vKQLY8E+pR/ko=
=Vt0d
-----END PGP SIGNATURE-----

Am 28.12.2011 21:24, schrieb Aaron Griffin:
> Hmm, who has the password to this these days? It's been changed and I
> can no longer access it.

Nobody has it. You need to generate a new random password (pwgen), log
into gudrun and set a new password with mmsitepass. That's what everyone
else has been doing for years.

On Fri, Dec 30, 2011 at 7:00 AM, Thomas Bächler <thomas@archlinux.org> wrote:
> Am 28.12.2011 21:24, schrieb Aaron Griffin:
>> Hmm, who has the password to this these days? It's been changed and I
>> can no longer access it.
>
> Nobody has it. You need to generate a new random password (pwgen), log
> into gudrun and set a new password with mmsitepass. That's what everyone
> else has been doing for years.

Actually the password was 'ragamuffin' for years until you and others
started doing it this way- it hadn't changed in years until about a
year ago.

-Dan

Am 31.12.2011 17:20, schrieb Dan McGee:
> On Fri, Dec 30, 2011 at 7:00 AM, Thomas Bächler <thomas@archlinux.org> wrote:
>> Am 28.12.2011 21:24, schrieb Aaron Griffin:
>>> Hmm, who has the password to this these days? It's been changed and I
>>> can no longer access it.
>>
>> Nobody has it. You need to generate a new random password (pwgen), log
>> into gudrun and set a new password with mmsitepass. That's what everyone
>> else has been doing for years.
>
> Actually the password was 'ragamuffin' for years until you and others
> started doing it this way- it hadn't changed in years until about a
> year ago.

Actually, I kept asking around for the password, and nobody knew it.