----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> a3a10750
@REPLY: <sagv7ip0r85gu0u73u2i3g59kp64nn6gd8@4ax.com>
6c5e8994
@REPLYADDR Paul <nospam@needed.invalid>
@REPLYTO 2:5075/128 Paul
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References:
<r8qu7i9ee9j58kh704dma61vse113v1uii@4ax.com> <0g3v7ita0bl40rgu0id77s1mge0roluhda@4ax.com> 1@dont-email.me>
<sagv7ip0r85gu0u73u2i3g59kp64nn6gd8@4ax.com>
@TZUTC: -0400
@PID: Ratcatcher/2.0.0.25 (Windows/20130802)
@TID: FIDOGATE-5.12-ge4e8b94
On 6/6/2023 7:33 PM, Char Jackson wrote:
> On Tue, 6 Jun 2023 19:07:47 -0400, Paul <
nospam@needed.invalid> wrote:
>
>> On 6/6/2023 3:54 PM, Char Jackson wrote:
>>> On Tue, 06 Jun 2023 13:54:16 -0400, micky <NONONOmisc07@fmguy.com>
>>> wrote:
>>>
>>>>
>>>> I forget if there is an active ng for internet questions. I would have
>>>> included it and I still could if someone would remind me.
>>>>
>>>> Planning to buy a wifi radio. Found what looks like the best radios. 3
>>>> of which are complete with presets Wanted to look at their portal.
>>>>
>>>> Online owners manual gives this address:
>>>> myradiosplus.gracedigital.com
>>>>
>>>> which, when entered, turns into this address
>>>>
>>>> https://myradiosplus.gracedigital.com
>>>>
>>>> That`s fine, except I get this error message (at the bottom***), but I
>>>> only get it on the desktop computer. On the laptop, connected to the
>>>> same router, it works. A blank registration page is displayed.
>>>>
>>>> Desktop computer running Win10 Pro v20H2 (build 19042.844)
>>>> Laptop computer running Win10 Home v22H2 (build 19045.3031)
>>>> Desktop Firefox v 113.0.2 64bit
>>>> Laptop Firefox same exact version
>>>>
>>>> So why are the results different?
>>>>
>>>>
>>>> ***Warning: Potential Security Risk Ahead
>>>> Firefox detected a potential security threat and did not continue to
>>>> www.myradiosplus.gracedigital.com . If you visit this site, attackers
>>>> could try to steal information like your passwords, emails, or credit
>>>> card details.
>>>>
>>>> What can you do about it?
>>>> This issue is most likely with the webiste and there is nothing you can
>>>> do to resolve it. You can notifiy he website`s administrator about the
>>>> problem.
>>>> Go Back (recommended) Advanced
>>>>
>>>> But advanced doesn`t let me proceed like it sometimes does.
>>>
>>> C:\\WINDOWS\\system32>curl -v www.myradiosplus.gracedigital.com
>>> * Trying 52.11.27.185:80...
>>> * Connected to www.myradiosplus.gracedigital.com (52.11.27.185) port 80
>>> (#0)
>>>> GET / HTTP/1.1
>>>> Host: www.myradiosplus.gracedigital.com
>>>> User-Agent: curl/8.0.1
>>>> Accept: */*
>>>>
>>> < HTTP/1.1 301 Moved Permanently
>>> < Date: Tue, 06 Jun 2023 19:49:18 GMT
>>> < Content-Type: text/html
>>> < Content-Length: 169
>>> < Connection: keep-alive
>>> < Server: nginx/1.20.0
>>> < Location: https://www.myradiosplus.gracedigital.com/
>>> <
>>>
>>> 301 Moved Permanently
>>>
>>> 301 Moved Permanently
>>>
nginx/1.20.0
>>>
>>>
>>> * Connection #0 to host www.myradiosplus.gracedigital.com left intact
>>>
>>> *******
>>>
>>> You should just navigate to https://www.myradiosplus.gracedigital.com/
>>> because when you navigate to the http URL all you get is a redirect to
>>> the https URL.
>>>
>>> As for the warning you received, it looks like a misconfiguration in
>>> that browser because what it should have done is silently follow the
>>> https redirect, just the like your other browser did.
>>>
>>
>> "Websites prove their identity via certificates. Firefox does not trust
>> this site because it uses a certificate that is not valid for
>>
>> www.myradiosplus.gracedigital.com.
>>
>> The certificate is only valid for the following names:
>>
>> gracedigital.com
>> *.gracedigital.com
>>
>> Error code: SSL_ERROR_BAD_CERT_DOMAIN
>
> It`s been a long day here and my eyes are tired, but the cert looks fine
> to me. Am I missing a typo or something? The wildcard cert should cover
> it, no? It works fine for me in 3 different browsers.
>
https://stackoverflow.com/questions/29018917/when-does-firefox-throw-ssl-error-b
ad-cert-domain-with-a-wildcard-certificate
"Note that *.example.com would
also match subdomain.example.com
but not foo.subdomain.example.com."
So it`s the usual thing, where people keep reinventing the
definition of a wild card.
Imagine the horror one day, when the old email tool I was
using could support c.d.e dot separated address, and then
my email provider at the time started using a.b.c.d.e instead.
The email tool had heart failure :-) The even neater bit of
trivia, is one of the users of that tool, did a *binary* patch
and fixed that. So it would accept kooky names. Worked
like a charm.
Paul
--- Ratcatcher/2.0.0.25 (Windows/20130802)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5005/49 5015/255 5019/40 5020/715 848 1042
4441 12000 5030/49 1081
SEEN-BY: 5075/128
@PATH: 5075/128 5020/1042 4441