Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
But, the first one has huge hardware requierements (written in Java). With the second, I've failed to install it just out-of-the-box.
Is it even safe, to manage such a tree via web UI ? The first problem, that comes to my mind, is that the software would have to have an access to the root.key which is rather inconvenient.
Nevertheless, how is it done in an enterprise?
Requirements:
platform: linux
cost: opensource
[UPDATE]
Found feature-rich solution. Maybe one would be interested in: DogTag PKI
Unfortunately, it's Fedora/RedHat/CentOS dependent. I'll try to use it under Debian and give a note, if succeeded.
[UPDATE]
I've abandoned DogTag.
Instead, I've installed and configured EJBCA. I really recommend it. It has many features, that are important (e.g. possibility to isolate CA from RA, group & permissions management, whole certificate life-cycle, and many more).
On the homepage, there's also LiveCD available, so if one want's to test, just go for it
Last edited by fiku; 05-05-2011 at 06:12 AM.
Reason: Update
No idea how this is generally done in an enterprise. I manage a small CA for my department, but I get by with openssl(1)'s handy CA.pl(1) interface.
Quote:
Originally Posted by fiku
Is it even safe, to manage such a tree via web UI ?
Short answer (IMO): not really!
Longer answer (IMO): sure - if you keep it on a highly restricted, hardened, non-Internet facing host. (It would of course be your responsibility to assess the level of risk and deploy accordingly.)
No idea how this is generally done in an enterprise. I manage a small CA for my department, but I get by with openssl(1)'s handy CA.pl(1) interface.
Actually, I use the same method right now. But it would be nice, to have some interface, when e.g. non-IT person could send a request for his/her certificate to be signed by CA or, as mentioned above, generating CRL (though it's quite simple done by CA.{pl,sh} - actually wrapped CA.{pl,sh} that also deploys the CRL to the WWW server).
I've abandoned DogTag.
Instead, I've installed and configured EJBCA. I really recommend it. It has many features, that are important (e.g. possibility to isolate CA from RA, group & permissions management, whole certificate life-cycle, and many more).
On the homepage, there's also LiveCD available, so if one want's to test, just go for it
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.