autosign
C R Ritson
Chris Ritson (Computing Officer and School Safety Officer)
Room 707, Claremont Tower, EMAIL: C.R.R...@ncl.ac.uk
School of Computing Science, PHONE: +44 191 222 8175
Newcastle University, FAX : +44 191 222 8232
Newcastle upon Tyne, UK NE1 7RU. WEB : http://www.cs.ncl.ac.uk/
Luke Bigum
autosigning does not clear off an old Agent's certificate, so you're
getting certificate mismatch errors. Puppet's RESTful API allows you to
manage certificates. It's been a long time since I tested this but I
have this in my auth.conf:
#allow hosts to manage certificates
#path /certificate_status/([^/]+)$
path /certificate_status/
auth any
allow *
And then I do this in a kickstart file to have each server delete it's
certificate before it generates a new one and contacts the Puppet Master
for the first time:
curl -k -X PUT -H "Content-Type: text/pson" --data
'{"desired_state":"revoked"}'
https://puppet:8140/production/certificate_status/$HOSTNAME
curl -k -X DELETE -H "Accept: pson"
https://puppet:8140/production/certificate_status/$HOSTNAME
Check out this page for more information:
http://docs.puppetlabs.com/guides/rest_api.html
-Luke
--
Luke Bigum
Information Systems
Ph: +44 (0) 20 3192 2520
luke....@lmax.com | http://www.lmax.com
LMAX, Yellow Building, 1A Nicholas Road, London W11 4AN
FX and CFDs are leveraged products that can result in losses exceeding
your deposit. They are not suitable for everyone so please ensure you
fully understand the risks involved. The information in this email is not
directed at residents of the United States of America or any other
jurisdiction where trading in CFDs and/or FX is restricted or prohibited
by local laws or regulations.
The information in this email and any attachment is confidential and is
intended only for the named recipient(s). The email may not be disclosed
or used by any person other than the addressee, nor may it be copied in
any way. If you are not the intended recipient please notify the sender
immediately and delete any copies of this message. Any unauthorised
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden.
LMAX operates a multilateral trading facility. Authorised and regulated
by the Financial Services Authority (firm registration number 509778) and
is registered in England and Wales (number 06505809).
Our registered address is Yellow Building, 1A Nicholas Road, London, W11
4AN.
C R Ritson
What are the security implications of allowing clients to manipulate certificates in this way? For now at least I will restrict this to the subset that are likely to need frequent rebuilds.
Chris Ritson (Computing Officer and School Safety Officer)
Room 707, Claremont Tower, EMAIL: C.R.R...@ncl.ac.uk
School of Computing Science, PHONE: +44 191 222 8175
Newcastle University, FAX : +44 191 222 8232
Newcastle upon Tyne, UK NE1 7RU. WEB : http://www.cs.ncl.ac.uk/
Luke Bigum
Regarding security, I was originally trying to work with this:
#allow a host to manage it's own certificate #path /certificate_status/([^/]+)$ path /certificate_status/ auth any allow $1Which was supposed to only allow a client to delete it's own certificate and only it's own. The $1 wasn't working for me though so I fell back to * (all hosts).
This allows all Agents full control of all operations under /certificate_status/, which basically means someone malicious could delete all your signed certificates, preventing all Agents from checking in. So definitely some implications ;-)
If you get auth.conf any more secure, let me know.
-Luke
C R Ritson
#allow (some) hosts to manage certificates
path ~ /certificate_status/test([^/]+)$
auth any
allow test$1
Then in the kick-start file I use Luke's suggested:-
# Revoke and delete any previous puppet certificate
curl -k -X PUT -H "Content-Type: text/pson" \
--data '{"desired_state":"revoked"}' \
https://puppet:8140/production/certificate_status/${HOSTNAME}.ncl.ac.uk
curl -k -X DELETE -H "Accept: pson" \
https://puppet:8140/production/certificate_status/${HOSTNAME}.ncl.ac.uk
I found I needed to add the domain name here to match the certificate that is generated later.
If auto-sign is to be avoided, one possibility is a hand-crafted script to look every so-often for new certificate requests and sign them if and only if they match some pre-determined pattern. Doing it this way avoids the lack of pattern matching in autosign.conf in which a * can only match a complete component of a fully qualified domain name and not some other arbitrary substring.
Chris Ritson (Computing Officer and School Safety Officer)
Room 707, Claremont Tower, EMAIL: C.R.R...@ncl.ac.uk
School of Computing Science, PHONE: +44 191 222 8175
Newcastle University, FAX : +44 191 222 8232
Newcastle upon Tyne, UK NE1 7RU. WEB : http://www.cs.ncl.ac.uk/
>-----Original Message-----
>From: Luke Bigum [mailto:Luke....@lmax.com]
>
>... Regarding security, I was originally trying to work with this:
>
>
>#allow a host to manage it's own certificate
>path /certificate_status/([^/]+)$
...
>allow $1
Bill Weiss
certificates, but not overwrite existing ones. At least, that's my
experience here :)
--
Bill Weiss
Backstop Solutions Group
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To post to this group, send email to puppet...@googlegroups.com.
>To unsubscribe from this group, send email to
>puppet-users...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/puppet-users?hl=en.
>
jcbollinger
On Apr 24, 11:45 am, Bill Weiss <bwe...@backstopsolutions.com> wrote:
> Autosign works, but not as you're expecting: it will sign new
> certificates, but not overwrite existing ones. At least, that's my
> experience here :)
"disable-authentication". Some people do actually seem to want that,
but Puppet does not offer it, and historically PuppetLabs has resisted
the idea. I don't blame them.
John
