Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+contesting\.com\s+invalid\s+security\s+certificate\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TowerTalk\]\s+contesting\.com\s+invalid\s+security\s+certificate\s*$/: 4 ]

Total 4 documents matching your query.

1. [TowerTalk] contesting.com invalid security certificate (score: 1): Author: "john@kk9a.com" <john@kk9a.com>; Date: Mon, 29 Jan 2018 09:37:30 -0500; I follow towertalk by reading the archives. For the last two days all three of my browsers say that contesting.com is an unsafe site and will not let me view it. John KK9A ___________________________; /archives//html/Towertalk/2018-01/msg00294.html (6,630 bytes)
2. Re: [TowerTalk] contesting.com invalid security certificate (score: 1): Author: K5CG <k5cg@hamoperator.org>; Date: Mon, 29 Jan 2018 17:10:03 -0600 (CST); It looks like the SSL certificate was replaced on January 22nd but they did not include the contesting.com domain in the common or alternate names fields of the cert. Common names admin.eham.net Alte; /archives//html/Towertalk/2018-01/msg00312.html (8,211 bytes)
3. Re: [TowerTalk] contesting.com invalid security certificate (score: 1): Author: <john@kk9a.com>; Date: Mon, 29 Jan 2018 20:08:57 -0500; Interesting, I am sure that they are aware of it now and will resolve the issue. John KK9A It looks like the SSL certificate was replaced on January 22nd but they did not include the contesting.com d; /archives//html/Towertalk/2018-01/msg00313.html (8,815 bytes)
4. Re: [TowerTalk] contesting.com invalid security certificate (score: 1): Author: Rob Atkinson <ranchorobbo@gmail.com>; Date: Tue, 30 Jan 2018 08:07:28 -0600; try not using https (SSL) Rob K5UJ _______________________________________________ _______________________________________________ TowerTalk mailing list TowerTalk@contesting.com http://lists.contest; /archives//html/Towertalk/2018-01/msg00315.html (7,535 bytes)

Current List: 1 - 4
Page: [1]