FYI,
I've finally got around to removing the old scripts. As the thread
pointed out they were all pretty broken and unmaintained.
Andrew
On 23 June 2015 at 09:54, Andrew Cagney andrew.cag...@gmail.com wrote:
I'd like to delete the old dist_certs shell script:
- dist_certs.py seems to be
On 24 June 2015 at 14:52, Paul Wouters p...@nohats.ca wrote:
On Wed, 24 Jun 2015, Andrew Cagney wrote:
Why did you pick east as the one to do the work on?
It's completely arbitrary. The VMs are identical.
Note we would need to update the kickstart file for pyOpenSSL
and opssibly other
| From: Andrew Cagney andrew.cag...@gmail.com
| This doesn't seem like a reason for retaining the old shell scripts -
| they are so far behind that they don't even generate all the required
| keys. BTW, best place to run dist_certs.py is on one of the test VMs
| (see make kvm-keys), and not on a
On June 24, 2015 11:34:53 AM EDT, D. Hugh Redelmeier h...@mimosa.com wrote:
| From: Andrew Cagney andrew.cag...@gmail.com
| This doesn't seem like a reason for retaining the old shell scripts -
| they are so far behind that they don't even generate all the required
| keys. BTW, best place to
On 24 June 2015 at 11:34, D. Hugh Redelmeier h...@mimosa.com wrote:
| From: Andrew Cagney andrew.cag...@gmail.com
| This doesn't seem like a reason for retaining the old shell scripts -
| they are so far behind that they don't even generate all the required
| keys. BTW, best place to run
On 24 June 2015 at 12:06, Matt Rogers mrog...@0x83.com wrote:
In the new certificate tests I made them always launch nic, to use it as the
ocsp and crl server available regardless of the vpn status. So I say we can
make nic flexible with its configuration, and let that handle cert
I don't think it is guaranteed that nic boots and runs the creation script
before the other VMs boot. It would add a slowdown if they do
Sent from my iPhone
On Jun 24, 2015, at 13:06, Matt Rogers mrog...@0x83.com wrote:
On June 24, 2015 11:34:53 AM EDT, D. Hugh Redelmeier
On Wed, 24 Jun 2015, Andrew Cagney wrote:
Why did you pick east as the one to do the work on?
It's completely arbitrary. The VMs are identical.
Note we would need to update the kickstart file for pyOpenSSL
and opssibly other pacakges for the guests. I don't really see
a good reason to
Fine with me
Sent from my iPhone
On Jun 23, 2015, at 10:54, Andrew Cagney andrew.cag...@gmail.com wrote:
I'd like to delete the old dist_certs shell script:
- dist_certs.py seems to be working
- make kvm-keys (assuming your VM is up-to-date) even lets you
generate keys when the host
I'd like to delete the old dist_certs shell script:
- dist_certs.py seems to be working
- make kvm-keys (assuming your VM is up-to-date) even lets you
generate keys when the host isn't Fedora 21.
little point in keeping old code around.
Andrew
___
On Tue, 23 Jun 2015, Antony Antony wrote:
I still have issues to install the patched pyOpenssl RPM on FC20
Can you be more specific?
Did you try:
wget ftp://ftp.nohats.ca/pyOpenSSL/pyOpenSSL-0.14-4.fc21.src.rpm
rpm -ihv pyOpenSSL-0.14-4.fc21.src.rpm
rpbuild -ba
I still have issues to install the patched pyOpenssl RPM on FC20. The patched
package is a barrier for me.
Of the 3 servers I run, so far I only manged to run distcert.py on one and I
copied the generated files to the other tow.
-antony
On Tue, Jun 23, 2015 at 12:25:48PM -0300, Paul Wouters
On Tue, 23 Jun 2015, Antony Antony wrote:
[root@blueswan ~]# rpmbuild -ba ~/rpmbuild/SPECS/pyOpenSSL.spec
error: Failed build dependencies:
python-sphinx is needed by pyOpenSSL-0.14-4.fc20.noarch
python-cryptography is needed by pyOpenSSL-0.14-4.fc20.noarch
python3-devel is
13 matches
Mail list logo
