[tei-council] Fwd: how do you use a TEI release?
stuart.yeates at vuw.ac.nz
Sun Feb 13 14:09:27 EST 2011
On 14/02/11 08:05, Sebastian Rahtz wrote:
> On 13 Feb 2011, at 18:51, stuart yeates wrote:
>> I'm surprising at how many of the responses were from the US, is that
>> normal for the TEI?
> there are a of TEI-L readers in the US, so maybe. hard to tell.
> anyway, I have taken the results at face value, and added steps to the TEI setup
> to create debian packages at each build. They need to be signed and published,
> of course, but I don't think I can automate that.
It is possible to automate the signing procedures, but I'm not sure how
convenient it would be in this case.
I believe it's done by generating a new key-pair explicitly for signing
and have both keys and passphrase on the build machine. The keys are
then less secure than the build machine, but if you ever have reason to
doubt the security of either you revoke the keys (which has less imact
because they're single-purpose keys).
Only the person operating the build machine should sign the keys.
The closest I can come to instructions for this is
Library Technology Services http://www.victoria.ac.nz/library/
More information about the tei-council