Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

HTTPS unsecure connection message with self-signed certificates

  • Gjin antwurden
  • 0 hawwe dit probleem
more options

Hello,

We are manufacturers of networking devices.

As most networking devices, ours can be configured by navigating to the default gateway IP address via the browser. With the rise of security awareness, various regulations are forbidding the usage of HTTP. This is bothersome to us, as connecting to our devices via HTTPS and our self-signed sertificates will always throw an error of an unsecure connection to the end user. We understand the technical reasoning for this and that users are able to ignore the message, but this does impact our user experience and it may even discourage users from using our devices.

As these regulations will be impacting networking devices globally, we want to ask you if there are any workarounds for the self-signed sertificate "unsecure connection" message. Perhaps there is an argument that can be set, or an ongoing effort from browser vendors to assist networking device manufacturers with this.

Any information or help is appreciated.

Thank you.

Hello, We are manufacturers of networking devices. As most networking devices, ours can be configured by navigating to the default gateway IP address via the browser. With the rise of security awareness, various regulations are forbidding the usage of HTTP. This is bothersome to us, as connecting to our devices via HTTPS and our self-signed sertificates will always throw an error of an unsecure connection to the end user. We understand the technical reasoning for this and that users are able to ignore the message, but this does impact our user experience and it may even discourage users from using our devices. As these regulations will be impacting networking devices globally, we want to ask you if there are any workarounds for the self-signed sertificate "unsecure connection" message. Perhaps there is an argument that can be set, or an ongoing effort from browser vendors to assist networking device manufacturers with this. Any information or help is appreciated. Thank you.

Jo moatte jo oanmelde by jo account om op berjochten te antwurdzjen. Stel in nije fraach as jo noch gjin account hawwe.