Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have 3 web servers all located behind it`s own public IP. Is it possible to make a wildcard for example non * in tinyCA, and how I proceed to get this to work?

I have searched google for help but has not found any good tutorial.

share|improve this question
If you know how to make one for in TinyCA, then just swap that for * wherever you put Wildcards actually require the client to check them, as far as the certificate goes, it actually issues one to * without * having a meaning – Jay Jun 23 '12 at 16:59

1 Answer 1

TinyCA is only an OpenSSL frontend, so if you search for it with openssl instead, you'll find more results.

Here is what I found:

mkdir /usr/share/ssl/certs/

cd /usr/share/ssl/certs/

(umask 077 && touch host.key host.cert host.pem)

openssl genrsa 2048 > host.key

openssl req -new -x509 -nodes -sha1 -days 3650 -key host.key > host.cert
...[enter * for the Common Name]...

openssl x509 -noout -fingerprint -text < host.cert >

cat host.cert host.key > host.pem

chmod 400 host.key host.pem


Consider reviewing the x509v3 certificate and joining the IRC channel on freenode for #openssl if you need realtime help. Most of the people on freenode on great.

However, back to the question at hand.

If you are operating web servers for yourself only, by all means, go with the self-signed route considering the cost. But, realize that many browsers are coming down harder on self-signed certs.

So, if you are serving to the public and want them to click on your site, or you are doing this for $, I'm going to recommend you get a commercial certificate instead.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.