Do you want to overwrite? (y/n): n - still overwrote #6
Comments
|
That shows you're still running v1.2.1.
Eric F Crist
…________________________________
From: Dan Langille ***@***.***>
Sent: Saturday, August 19, 2023 9:04:20 PM
To: ecrist/ssl-admin ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [ecrist/ssl-admin] Do you want to overwrite? (y/n): n - still overwrote (Issue #6)
This is ssl-admin 1.3.0
When I [unintentionally] said no, it proceeded and overwrote. I'm posting this only in case it did the wrong thing.
Menu Item: 4
Please enter certificate owner's name or ID.
Usual format is first initial-last name (jdoe) or
hostname of server which will use this certificate.
All lower case, numbers OK.
Owner []: bacula-sd-04.int.unixathome.org
File names will use bacula-sd-04.int.unixathome.org.
Please enter certificate owner's name or ID.
Usual format is first initial-last name (jdoe) or
hostname of server which will use this certificate.
All lower case, numbers OK.
Owner [bacula-sd-04.int.unixathome.org]:
bacula-sd-04.int.unixathome.org already has a key. Creating another one will overwrite the existing key.
bacula-sd-04.int.unixathome.org already has an active key. Do you want to overwrite? (y/n): n
Please enter certificate owner's name or ID.
Usual format is first initial-last name (jdoe) or
hostname of server which will use this certificate.
All lower case, numbers OK.
Owner [bacula-sd-04.int.unixathome.org]:
Would you like to password protect the private key (y/n): n
Generating a RSA private key
.....................................++++
...............................................................................................................................................++++
writing new private key to 'bacula-sd-04.int.unixathome.org.key'
-----
===> Serial Number = 80
=========> Signing request for bacula-sd-04.int.unixathome.org
Using configuration from /usr/local/etc/ssl-admin/openssl.conf
Enter pass phrase for /usr/local/etc/ssl-admin/active/ca.key:
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName :PRINTABLE:'US'
stateOrProvinceName :PRINTABLE:'PA'
localityName :PRINTABLE:'[redacted]'
organizationName :PRINTABLE:'[redacted]'
commonName :PRINTABLE:'bacula-sd-04.int.unixathome.org'
emailAddress :IA5STRING:'[redacted]'
Certificate is to be certified until Aug 17 02:00:29 2033 GMT (3650 days)
Write out database with 1 new entries
Data Base Updated
=========> Moving certificates and keys to /usr/local/etc/ssl-admin/active for production.
Can I move signing request (bacula-sd-04.int.unixathome.org.csr) to the csr directory for archiving? (y/n): ===> bacula-sd-04.int.unixathome.org.csr moved.
=====================================================
# SSL-ADMIN v1.2.1 #
=====================================================
Please enter the menu option from the following list:
1) Update run-time options:
Key Duration (days): 3650
Current Serial #: 81
Key Size (bits): 4096
Intermediate CA Signing: NO
2) Create new Certificate Request
3) Sign a Certificate Request
4) Perform a one-step request/sign
5) Revoke a Certificate
6) Renew/Re-sign a past Certificate Request
7) View current Certificate Revokation List
8) View index information for certificate.
i) Generate a user config with in-line certifcates and keys.
z) Zip files for end user.
dh) Generate Diffie Hellman parameters.
CA) Create new Self-Signed CA certificate.
S) Create new Signed Server certificate.
C) Generate new Certificate Revokation List (CRL)
q) Quit ssl-admin
Menu Item: q
[2:00 mydev dan /usr/local/etc/ssl-admin/active] % ls -l bacula-sd-04.int.unixathome.org*
-rw-r--r-- 1 root wheel 7330 2023.08.20 02:00 bacula-sd-04.int.unixathome.org.crt
-rw------- 1 root wheel 3272 2023.08.20 02:00 bacula-sd-04.int.unixathome.org.key
-rw-r--r-- 1 root wheel 7330 2023.08.20 02:00 bacula-sd-04.int.unixathome.org.pem
[2:00 mydev dan /usr/local/etc/ssl-admin/active] %
—
Reply to this email directly, view it on GitHub<#6>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANXQPYLGY6FVZULT3QCHWLXWFWCJANCNFSM6AAAAAA3W6M2WQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
I'm looking into that now, because something is up: |
|
It's not me, it's you? https://github.com/ecrist/ssl-admin/blob/v1.3.0/perl/ssl-admin#L261 says 1.2.1 Looks like |
|
You're using the source file github tagged, not the tar.gz or .xz file I published in the release.
Eric F Crist
…________________________________
From: Dan Langille ***@***.***>
Sent: Saturday, August 19, 2023 9:54:57 PM
To: ecrist/ssl-admin ***@***.***>
Cc: Eric F Crist ***@***.***>; Comment ***@***.***>
Subject: Re: [ecrist/ssl-admin] Do you want to overwrite? (y/n): n - still overwrote (Issue #6)
It's not me, it's you?
https://github.com/ecrist/ssl-admin/blob/v1.3.0/perl/ssl-admin#L261 says 1.2.1
Looks like ~~~VERSION~~~ didn't get populated right.
—
Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANXQP2WLL3Y3NBHDSGTKLDXWF4ADANCNFSM6AAAAAA3W6M2WQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is ssl-admin 1.3.0
When I [unintentionally] said no, it proceeded and overwrote. I'm posting this only in case it did the wrong thing.
The text was updated successfully, but these errors were encountered: