@dalias @bob_zim @ieure @chris @porglezomp pretty much...

past oral no mad's posts Post Back to profile

@dalias @bob_zim @ieure @chris @porglezomp pretty much any browser will throw up a warning if you make an HTTPS connection to a website with a self signed cert too.

Like 7 August at 21:47 | Wall-to-wall | Open on mastodon.social

5 comments

past oral no mad

@distinct @dalias @bob_zim @chris @porglezomp I also think this behavior is horseshit.

7 August at 21:49 | Open on retro.social

Brendan B.

@ieure @dalias @bob_zim @chris @porglezomp lol so noted.

7 August at 21:50 | Open on mastodon.social

past oral no mad replied to Brendan

@distinct @dalias @bob_zim @chris @porglezomp It's not the same, though: the browser explicitly tells you exactly what the problem is, and offers options for you to choose what to do (proceed or not).

macOS does not do this.

7 August at 21:52 | Open on retro.social

Chris Alemany🇺🇦🇨🇦🇪🇸 replied to past oral no mad

@ieure @distinct @dalias @bob_zim @porglezomp
Sorry, you lost me. There is a pretty clear explanation why this is happening. I am not going to get hung up on the word “Damaged” vs. Something else. It’s not a secret, including the workaround, all someone who really doesn’t want to sign their application has to do is inform their users of the workaround. As others have said, application signing is a pretty reasonable default behaviour to protect the millions of general users.

7 August at 22:02 | Open on mstdn.chrisalemany.ca

Rich Felker

@distinct @bob_zim @ieure @chris @porglezomp The browser doesn't lie and say the DNS lookup failed or the host is unreachable. It says the certificate is untrusted and asks you how to proceed.

7 August at 22:04 | Open on hachyderm.io