Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
I want to use the ./revoke-full "Client_Name" command to revoke a key:
1- Suppose I have two clients with the same name (Jason). I have generated the keys for one and not for the other. Now I revoke Jason's keys and generate new keys again with Jason's name. Because new keys with the same name are generated, can the previous Jason connect to the server?
2- Is the following command enough to refresh the CRL lifetime?
1. No, the previous Jason (with the revoked keys) cannot connect to the server that you are looking for. When verifying certificates, server always look for unique identifier, not just the name.
You can follow practice of using unique client names for each set of keys. This will have more clarity and simplified management.
2. And, yes the command is sufficient to refresh the CRL lifetime
1. No, the previous Jason (with the revoked keys) cannot connect to the server that you are looking for. When verifying certificates, server always look for unique identifier, not just the name.
You can follow practice of using unique client names for each set of keys. This will have more clarity and simplified management.
2. And, yes the command is sufficient to refresh the CRL lifetime
Code:
./easyrsa gen-crl
Hello,
Thank you so much for your reply.
What is the default CRL lifetime?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.