From: Olivier Turlier <o.turlier@gmail.com>
To: dev-context@ntg.nl
Cc: ntg-context@ntg.nl
Subject: Re: [NTG-context] updated Ubuntu edgy texlive+context backports
Date: Thu, 31 May 2007 13:54:03 +0000 (UTC) [thread overview]
Message-ID: <f3mk1r$4t3$3@sea.gmane.org> (raw)
In-Reply-To: <E1Htkaf-0001kv-00@skye.ra.phy.cam.ac.uk>
Le Thu, 31 May 2007 14:21:21 +0100, Sanjoy Mahajan a écrit:
>> Can you give the location of your key
>
> Sure, I just figured out how to do key stuff...
>
> I've submitted it to hkp://subkeys.pgp.net and it is available from
> there and other keyservers (search for 'sanjoy mahajan' or for the DSA
> id 0x3FCDAAA3). You can also get the ascii exported key here:
>
> <http://www.inference.phy.cam.ac.uk/sanjoy/sanjoy.asc>
>
> [For those just getting up to speed with secure apt (which includes
> me), here is how to add a public key to apt's keyring:
>
> wget http://www.inference.phy.cam.ac.uk/sanjoy/sanjoy.asc -O - \
> | apt-key add -
>
> Then apt-get can verify the signatures on the packages downloaded from
> my web.mit.edu site (which I signed with the private key corresponding
> to that public key).]
>
> -Sanjoy
>
> gpg DSA: 0x3FCDAAA3
> gpg fp: 9722 56B0 F787 12A9 164E 34B7 09C9 E543 3FCD AAA3
I'v pbs whith the command for having the packages signed with your key.
Found similar commands, but with a *.gpg* file, like this one :
wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key
add - && sudo apt-get update
So maybe a solution is to provide one on your website. Thanks
Olivier
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
prev parent reply other threads:[~2007-05-31 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 12:26 Sanjoy Mahajan
2007-05-31 8:18 ` Olivier Turlier
2007-05-31 13:21 ` [NTG-context] " Sanjoy Mahajan
2007-05-31 13:54 ` Olivier Turlier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f3mk1r$4t3$3@sea.gmane.org' \
--to=o.turlier@gmail.com \
--cc=dev-context@ntg.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).