network profile
| bio | website | |
|---|---|---|
| location | Russia | |
| age | ||
| visits | member for | 6 months |
| seen | Nov 23 '12 at 7:46 | |
| stats | profile views | 0 |
Patiently awaiting of zombie apocalypse
|
Nov 22 |
awarded | Supporter |
|
Nov 22 |
comment |
Issuing SSL certificates for device automation software package without domain names Thanks for the answer. Yep, we certainly do not have control over the client side: they will use standard web browsers. So our task is too ensure that the server will have the domain name and request a certificate for that server (or a group of them). We were thinking right, we were just not completely sure: kinda new to that SSL stuff. Thanks again! |
|
Nov 22 |
awarded | Student |
|
Nov 22 |
comment |
Issuing SSL certificates for device automation software package without domain names Thanks for you quick response! |
|
Nov 22 |
comment |
Issuing SSL certificates for device automation software package without domain names Thanks for you quite decent explanation! Domain names for our server components are not really our issue since we just provide the software package to a customer's network. Then they can run the server using plain IP addresse OR they certainly can register the domain name. But from what I know they dont go with DNS: if its ok with them to use IP address only - they wont need DNS, saves them a bit of trouble. Due to specific reasons we cannot push them to register domain name. But we of course trying to explain the benefits of it. |
|
Nov 22 |
asked | Issuing SSL certificates for device automation software package without domain names |
