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.
I´m searching for a way to use HTTPS without installing a certificate on the connecting client.
-> have apache running and a directory-directive with SSLRequireSSL
-> build my own CA and configured it in httpd.conf
=> all fine
now, is it possible and how, that the client (browser) which connects to my site (with own-build CA!) accepts the SSL connection or can this only be realised with official certificates?
hope someone can help and u understand my intention ;-)
Not sure I understand... but it sounds like you just need to get yourself a signed certificate. Try going to www.freessl.com. The name is a little misleading. I don't think they actually offer free certs. But you can pay like $50 and get a cert that is signed by a reputable authority and will be valid for 1 year. This way, when your server presents the cert to the client, they will already have knowledge of the cert authority and the end user should not see any warnings.
If you dont want to pay the money, I think your only option is to sign the cert yourself and live with the warning messages on the clients end. They will still be protected by SSL, but the warning may give some people (read: inexperienced users) some concerns.
Originally posted by Donboy ... I think your only option is to sign the cert yourself and live with the warning messages on the clients end. ...
Yes, all ok. The problem is M$ IE. with other browsers theres no problem,because if you come to a site, you can accept the cert (permanently) and all is good. But the IE DON´T always "save" the cert correctly, so the warning messages are inconvenient.
the only way seems to import the selfsigned cert manually on each client! :-(
theres a new problem. have 2 clients here (winxp, IE) with no certs or CA entry imported.
when trying to connect to https://my.domain.tld they got a DNS-error message (host could not be found) !!!!???
after import of cert all went fine, so it must be the cert or some config of httpd !!!???
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.