> admin/admin is not great security hygiene but you’ve reduced most of the risk by airgapping.
replyadmin/admin is on a post-it stuck to the monitor because everyone we hire is perfectly capable of rooting a machine they have physical access to.
[dead]
replyJust my opinion but I believe a self-signed is more secure than Let’s encrypt. When a self-signed cert changes and no one in the org knows why that is alarming. Getting certificate error messages every month and half every numbs the org to the alarm.
replyI'm not sure if you're speaking from personal experience, but most I've interacted with don't have to worry about the self-signed vs. LetsEncrypt debate. They just don't do it. Also there would be no way to do LetsEncrypt as the system is air gapped.
replyYou can do DNS challenges for air gapped networks as long as the TXT records resolve publicly.
replySo then you have a signed CSR right? How would you get the certificate onto the box?
reply> Rotating LetsEncrypt certs on the system every 45 days is a lot of toil
replyWhat is unique about your system using LetsEncrypt that you can't automate certbot to handle this task as it was designed and intended to be done?
On an airgapped system that is is turned on once and needs to keep running for many, many years? Industrial equipment is a world of its own and internet best practices just don't transfer directly.
replySome PLCs run extremely expensive machines. Some machines can't afford to have their control systems stutter or fail because that can lead to physical damage and production outages of enormous proportions. A PLC that stops communicating because a certificate just expired is absolutely not acceptable in some plants.
Running certbot on your web server is easy.
replyRunning certbot on a random PLC isn't happening.