bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <>
Subject Re: new KEYS scheme? (Was: Re: [VOTE] Release Apache Bloodhound 0.4 (incubating))
Date Tue, 15 Jan 2013 11:22:44 GMT
On 15/01/13 10:56, Nick Burch wrote:
> On Tue, 15 Jan 2013, Gary Martin wrote:
>> I don't know if there is a plan to make this even less work but I 
>> think we could probably keep the KEYS file up to date by:
>>   wget -O KEYS
>> and committing any changes.
>> Does anyone know more about all this though?
> There has been some discussions about this in the last few weeks (most 
> on the infrastructure list, if memory serves). As long as everyone has 
> their current key in LDAP, then that's a good way to keep the list 
> current. However, the KEYs file should generally also contain the list 
> of past keys too, so people can use it to verify old releases too. To 
> that end, you probably want to use the LDAP generated keys file to 
> append to your keys list, not replace it, so the old keys remain there 
> too. It's a few more steps than just a wget+commit, but not many!
> Nick

Ah, thanks for that; good point there. It may not be hugely complicated 
but I might write a script to do the job so that we don't have to worry 
too much about manually working out which entries are new and which are 
no longer in the bloodhound.asc file.


View raw message