Hmm... some software doesn't recognize multilevel wildcards and rejects the certificate, but I don't think it requires any hardware changes (unless we're talkin

Hmm... some software doesn't recognize multilevel wildcards and rejects the certificate, but I don't think it requires any hardware changes (unless we're talking about hardware TLS accelerators). Basically, browsers and other TLS clients have to implement RFC 6125 if they still don't. Edit: my mistake, RFC6125 actually seem to forbid those (I thought it was allowing them - was wrong). That's sad. Guess, there is just no way to have TLS for what I want. Have to stick with plain HTTP.