[Opendnssec-develop] Access to test environment

Jerry Lundström jerry at opendnssec.org
Mon Sep 17 08:33:25 UTC 2012

Hi all,

So I've been thinking about how to solve the access to the test environment.

I've looked at Crowd (that we use for JIRA, Confluence, FishEye etc) but it can't really be accessed in a simple way, like LDAP or PAM.

So, to make it easy we will use a authorized_keys file that we will keep in SVN and it will be updated on each machine via cron. All you have to do is to add the public part of an ssh key you make for this (please make a unique for this, don't use already existing keys) and wait a few minutes and you have access to all the machines.

Now the access everyone will get is readonly@<machine> and it will be able to read all the logs from the tests and system messages. You won't be getting access to the jenkins user because I don't want the risk off people leaving changes or turning off tests locally. But fear not, it will be possible to test tests locally with the readonly user later on.

I will be setting this up today and removing other accounts that has been made before for testing purposes.

Jerry Lundström - OpenDNSSEC Developer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20120917/6bd70683/attachment.bin>

More information about the Opendnssec-develop mailing list