chiark / gitweb /
Allow different peer associations to use different private keys.
authorMark Wooding <mdw@distorted.org.uk>
Wed, 25 Jan 2012 23:49:47 +0000 (23:49 +0000)
committerMark Wooding <mdw@distorted.org.uk>
Mon, 7 May 2012 14:35:11 +0000 (15:35 +0100)
commitfe2a5dcf9de1f124ed3cfa2c6327860bd5aca820
treec90195f56901b764c975d94100ae5e6f76115ce0
parent35c8b547dde529693875087d67fa60bf88319d2b
Allow different peer associations to use different private keys.

Add a `peertag' slot to the `peerspec' structure stating which private
key to use; a null pointer means to use the default `tag_priv'.  Add a
`p_privtag' function to retrieve the private key tag to use.

The ADD command now has a `-priv' option which sets this slot
appropriately.  The `connect' service fetches a `priv' key. from the
database to set this option.
peerdb/peers.in.5.in
py/tripe.py.in
server/admin.c
server/keyexch.c
server/peer.c
server/tripe-admin.5.in
server/tripe.h
svc/connect.in