![]() ![]() Then the browsers will accept the certs that you issue, without needing to involve any outside party. If you can get the museums to make a change to the browser configuration you can issue certs without the involvement of an external CA: you can make your own CA for your application (perhaps just by using a few openssl command line commands, among other possibilities) and then ask the museums to add the CA’s root certificate to the kiosk browsers. I can then make the app (which is faking DNS) redirect all users to which is still just the same server but as it would be providing the correct certificate would that work completely disconncted from the internet? Maybe they can register it to a domain like “ ”. Users connect to the WiFi, using fake DNS and Captive Portal support they either wait for the captive portal stuff to kick in and get automatically connected to the installation (iOS) OR they type any domain name like h.com and get redirected to the installation (android/winphone).Īs there’s no connection to the internet I’m curious if there is a possible solution.īasically instead of me having to provide a certificate museums can get a free one from Let’s Encrypt and install it locally in the app. My native app (OSX/Win/Linux) is also used in a bunch of museums and installations. Actually could Let’s Encrypt help with the second path I mentioned above. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |