Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Chromium and self-signed certificates
Date: Wed, 14 Aug 2024 07:08:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <v9hl56$bu9i$2@dont-email.me>
References: <v9g9tq$14v2$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 14 Aug 2024 09:08:22 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="09768462440b3e073b404311a341494e";
	logging-data="391474"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Fji22k7WSQ5zmWIk/yQPg"
User-Agent: Pan/0.159 (Vovchansk; )
Cancel-Lock: sha1:+rTvXb4BGkbFR2+qwa9Jwn96juI=
Bytes: 1432

On Tue, 13 Aug 2024 18:50:34 -0000 (UTC), bp wrote:

> I'm trying to get chromium under RasPiOS to open an https connection to
> a private webserver that's using a self-signed certificate.

The usual way I would do this is create your own CA (root) cert as the 
self-signed certificate; then the actual SSL certificate that the server 
is using will be signed with this certificate.

On the browser side, import the CA cert into the key store, and it will 
automatically trust certs signed with this CA cert.