Does that work? In the past when I created a self-signed cert (for
Apache on Linux), adding it to the trusted certs didn't work (at least
in Chrome). I still got the evil warnings. I ended up creating my own
CA, used that to sign the web cert, and then copied the CA to the
trusted certs in Chrome. Then I gave out the CA to the folks I work
with who needed to access the web page, and they did the same. That was
easy and cheap for a small group of known users.
On 8/28/2023 3:38 PM, Peter Vels wrote:
It's not about the port. You need to add the self-signed certificate to
Firefox’s list of trusted certificates.
On Tue, 29 Aug 2023 at 05:50, Radoslaw Skorupka <
00000471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:
Disclaimer: I know it is much better idea to use "regular" certificate
signed by CA instead of self-signed one. However I have to work on some
HMC which use self-signed certificate.
So far, so good.
When I connect first time I get warning message on my Firefox browser. I
accept the risk and further connections do not raise an alarm.
However some new windows use HMC address and different port, like 99xx.
Everytime a new port is used the warning is issued again and again.
Question: is there any method to customize Firefox to accept the same
certificate coming from same HMC address on *any port*?
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
