X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm2; bh=2LGYLuoSkVdLFE8xt4GUvOAbPQVo1
	E/tDMsXM0iybNg=; b=uwjpP3dBkd5Ydd2CzwTqakLV4wthcSC7ZePzOp2bFo5Jw
	HgYHl1YOW1T8zIcjCdIXXI2Nveob0jmbHrlE/G9ufujQOoesxEF1kxfkk0i6sQ47
	5PHU4l3qX6I3gZ9003+KSFucPVrHED0er1wcv8XuXXLWpmBJcNpVFjGN8eB510w5
	oFqSS3J8zd+T7Mazn27kxI5GsWQMe6cPJGOeV43fztwL39iTsuOCFyPLT8csLfwj
	JcKN7np2TJM2gTMbVfuLaorTJW05dRKLL0gD+2TOpeeQYAZXcLTl3tjfRAX2vUC9
	KPCizqBob4X4r9xOCL0RQTK21gGpLNEsRipJ6RhnQ==
X-ME-Sender:	<xms:oqkpYL-N9omrSueA6ctzacpkp-oukxfGpS4vhDXjC10FwzYu_01RFA>
	<xme:oqkpYHsQXtedfSon0UAKGJ3nNZIEVyMV1_AgpO0h-9aUda6Ai5Kfvi00_cFD23e5U
	Gktak1PrFELnaDYag>
X-ME-Proxy-Cause:	gggruggvucftvghtrhhoucdtuddrgeduledrieeigddtvdcutefuodetggdotefrodftvf
	curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
	uegrihhlohhuthemuceftddtnecunecujfgurheprhfuvfhfhffkffgfgggjtgfgsehtje
	ertddtfeejnecuhfhrohhmpefiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghs
	thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepteejvedtieehvdfgfefftdevff
	euleduleejiedtffeiveeuvefgkeehiedtffehnecuffhomhgrihhnpehlvghtshgvnhgt
	rhihphhtrdhorhhgpdhgihhthhhusgdrtghomhdplhhinhhugihquhgvshhtihhonhhsrd
	horhhgnecukfhppedutdekrddvudehrdduleehrddvtdehnecuvehluhhsthgvrhfuihii
	vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhhvghrrhhlsehfrghsthhmrghilh
	drtghomh
X-ME-Proxy:	<xmx:oqkpYJDenwimAKu9ZZj4_3C_kVBsu7lhx_ORFrDTt0R3rEdQUYCiNg>
	<xmx:oqkpYHePqp-MoJjq16mSipcIKVV0clCOPvIrtgd_fpj3MVexcxwrag>
	<xmx:oqkpYAPEe-gdEfz42-99PGanuDxELXSfGbi_OpE_6X75KBN51mZEEA>
	<xmx:o6kpYGZRvZQeYvZ2gLRnPUVh1IoGSfBwmSCFWV7K4D3SxtwPhZl2q2cTZBY>
Subject:	Re: [geda-user] No https for pcb-rnd
To:	geda-user AT delorie DOT com
References:	<bde96a88-b800-6222-6138-69de5d03f0c2 AT fastmail DOT com>
	<20210110065529 DOT A5C7E82966EF AT turkos DOT aspodata DOT se>
	<20210214212322 DOT DAE81807BE6E AT turkos DOT aspodata DOT se>
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<d29c68d0-9052-b397-1a88-200c3864eb49@fastmail.com>
Date:	Sun, 14 Feb 2021 14:49:22 -0800
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
	Thunderbird/68.12.0
MIME-Version:	1.0
In-Reply-To:	<20210214212322.DAE81807BE6E@turkos.aspodata.se>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 2/14/21 1:23 PM, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> Karl Hammar:
>> Girvin Herr:
>>> In the name of computer security, I am going through all of my browser
>>> bookmarks and rejecting all websites that do not support the https
>>> protocol.
>> ...
>>
>> So would a self signed certificate suffice -- since then you are using
>> "https".
> I found out that you can use https://letsencrypt.org/ instead of a
> self-signed cert:
>   Let's Encrypt is a free, automated, and open certificate authority
>   brought to you by the nonprofit Internet Security Research Group (ISRG).
>
> It was pretty simple to get it to work with
>   https://github.com/diafygi/acme-tiny
>
> Feel free to ask me if you need any help with setting it up.
>
> Regards,
> /Karl Hammar
>
Karl,

Thanks for the information. I will make note of it in case I need it. 
This thread is a bit old, but since I last posted to it, I had 
discovered that many websites that do not use https for their home page, 
do use it for their e-business login, so I don't have a problem with 
them. It is the ones who conduct business in the clear that I put in 
quarantine and they were few. A while back, Firefox was complaining 
about my login to LinuxQuestions.org. They were conducting my login in 
the clear. They have since corrected that error.

As for certificates, Slackware does update the "ca-certificates" package 
fairly regularly, so I have not been having any problems with 
certificates. The last time I was having a certificate problem was when 
my CMOS battery ran low without my notice and caused the certificate 
time checks to fail. Once I replaced the battery and re-set the clock, 
everything ran fine again.

Thanks again for the info and take care.

Girvin

- Raw text -