Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revoking a existing using cert making other cert disable too #25

Closed
robiiinos opened this issue Jan 12, 2017 · 4 comments
Closed

Revoking a existing using cert making other cert disable too #25

robiiinos opened this issue Jan 12, 2017 · 4 comments

Comments

@robiiinos
Copy link
Contributor

robiiinos commented Jan 12, 2017

Hi,

I've found something by using your script. After adding one or many users with your scripts; when I try to revoke a existing user; it revoke him but also make all other cert unaivalable to use. Any other cert remaining on the current server are like "disabled" and even deleting all cert and re-making them one by one doesn't func...

[French]
Bonjour;
J'ai vu en utilisant ton script et après avoir ajouter plusieurs utilisateurs; que lorsqu'on en revoke un seul, tous les autres cert sont unitilsables... Plus aucun ne marche peut importe la configuration :(
Même en supprimant toutes les cert et en les re-créant; cela ne marche pas...

PS : J'attend impatiemment la màj pour OpenVPN 2.4.0 pour Debian et les DNS locaux 👍

@robiiinos
Copy link
Contributor Author

Solved by myself adding : chown nobody:nogroup /etc/openvpn/crl.pem
In the step when revoking a user cert; like idk why it wasn't func on my server if other do 👎

@angristan
Copy link
Owner

Was it on your side or is it a script's bug ?

@angristan
Copy link
Owner

Apparently it is a script's bug #32

@angristan angristan reopened this Feb 6, 2017
@borowskiio
Copy link

borowskiio commented Feb 25, 2017

Hi.

It turns out that when revoking a client, script manipulates a crl.pem file - and it gives it wrong permissions of being readable only by the owner.

I added read permission for the group and others (as per dh.pem) and it went through.

I noticed it after reading through a syslog and a line:

ovpn-server[3668]: xxx.xx.xx.xxxx:3987 CRL: cannot read: crl.pem

Perhaps the script needs setting the umask at some point?

angristan added a commit that referenced this issue Jun 25, 2017
A client revocation would make crl.pem unreadable and thus blocking any other client to connect.

Fixes #47, #25 and #49.
@robiiinos robiiinos changed the title Revokign a existing using cert making other cert disable too Revoking a existing using cert making other cert disable too Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants