wondering #why a selfsigned #certificate based #https connection is bad, while no #browser complains about #unencrypted #http connections

Gerelateerd

• murbed 28 Aug ´15 Still waiting for pipe-lining to become mainstream
• murbed 28 Aug ´15 My ranting was fair: We're still waiting for pipe-lining to become mainstream
• shared 12 May ´17 Uncensorable Wikipedia on IPFS
• murbed 05 Aug ´16 Let’s encrypt! It’s easy!
• murbed 15 Aug ´14 Setting up https/spdy communication for your website with nginx
• murbed 06 Sep Generating and parsing data URI's in Ruby
• delicious 08 Apr Protomaps - A free and open source map of the world
• shared 22 Aug @beka_valentine@kolektiva.social “I cringe every time I use a browser for many reasons. The browser…
• murbed 23 Mar Browserondersteuning
• delicious 23 Sep AVIF has landed
• murbed 05 Jun Bye Internet Explorer
• murbed 30 Oct How to REST?
• murbed 20 Sep Considering online generation of certificate requests
• murbed 18 Oct ´18 Het groene slotje en Symantec
• shared 10 Apr ´18 Navigating to Success: You don’t need a road map, just a moral compass
• murbed 05 Mar ´18 Becoming your own local certificate authority (and issue your first certificate)
• delicious 07 Oct ´17 Web Compatibility
• shared 06 Aug ´17 The Back Up Question: Defining a Project’s ‘Good Enough’
• twitter 09 Jan ´17 Dan pas @RPlasterk? “uiterlijk(!) eind 2017 versleutelde verbindingen overal op overheidswebsites” https://www.rijksoverheid.nl/documenten/kamerstukken/2017/01/09/beantwoording-kamervragen-berichten-helft-websites-overheid-onveilig-en-veel-overheid-websites-onnodig-onveilig #https
• twitter 09 Jan ´17 nb: slechts “waar persoonsgegevens en andere gevoelige gegevens worden gecommuniceerd” #https #privacy
• twitter 03 Aug ´16 @svandragt with @letsencrypt there is no excuse anymore for not using #https (it's very easy) Other I don't know :o