---
.../nodes/sign-vault1.fedora.phx.redhat.com.pp |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp
b/manifests/nodes/sign-vault1.fedora.phx.redhat.com.pp
index 4c57d01..912d050 100644
---
Add a sigul module with bridge and server classes.
Adjust the sign-bridge1 node to use the new classes.
---
.../nodes/sign-bridge1.fedora.phx.redhat.com.pp| 17 +++-
modules/sigul/files/server.conf| 47 ++
modules/sigul/manifests/init.pp|
Here is my initial stab at a class for the signing server(s).
There is a bridge that clients communicate with (and I'm thinking
of forcing this through an ssh tunnel through bastion) and that
interacts with koji. There is also the server itself that has
the gpg keys on it and does the signing
On 2009-07-25 03:53:23 AM, Jesse Keating wrote:
There is a bridge that clients communicate with (and I'm thinking
of forcing this through an ssh tunnel through bastion) and that
interacts with koji. There is also the server itself that has
the gpg keys on it and does the signing action. The
On Sat, 2009-07-25 at 00:14 -0400, Ricky Zhou wrote:
Looks excellent to me, my only two comments are that you might want to
make the files:
/var/lib/sigul/.fedora-server-ca.cert
/var/lib/sigul/.fedora.cert
require = Package[sigul],
as well since they require the /var/lib/sigul
Add a sigul module with bridge and server classes.
Adjust the sign-bridge1 node to use the new classes.
Have sign-vault1 use the sigul::server class to get its
configuration
---
.../nodes/sign-bridge1.fedora.phx.redhat.com.pp| 17 +++-
.../nodes/sign-vault1.fedora.phx.redhat.com.pp |
