Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eweka.nl!lightspeed.eweka.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: Bernd Paysan Newsgroups: comp.lang.forth Subject: Re: Heartbleed detector Date: Sat, 12 Apr 2014 15:16:47 +0200 Organization: 1&1 Internet AG Lines: 24 Message-ID: References: <69fa4f94-8952-4aed-968d-23f1f0b0c630@googlegroups.com> NNTP-Posting-Host: p4ffb9415.dip0.t-ipconnect.de Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Trace: online.de 1397308608 6086 79.251.148.21 (12 Apr 2014 13:16:48 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Sat, 12 Apr 2014 13:16:48 +0000 (UTC) User-Agent: KNode/4.11.5 Xref: csiph.com comp.lang.forth:29568 visualforth@rocketmail.com wrote: > On Friday, April 11, 2014 6:39:18 PM UTC-4, Bernd Paysan wrote: > >> > On Friday, April 11, 2014 2:35:10 PM UTC-4, Bernd Paysan wrote: >> >> https://www.forth-ev.de/wiki/doku.php/examples:heartbleed > >> No, you just need to trust CACert and import their root certificate in >> your browser, which has 600 untrustworthy root certificates, because they >> paid Netscape money (more than 10 years ago) to be included. > > You are right, that works, too. > I preferred the easier way - > because such a warning never showed up before when visiting > www.forth-ev.de Yes, that's the problem why security doesn't work: Instead of doing something, you preferred to not use security at all. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/