[email protected] writes:
> I don't know about the XecureBrowser itself, but secure browser operating
> systems is a huge research area at present. SSL *has* been cracked ---
> there're a couple of known timing and man-in-the-middle attacks --- but if
> you use good keys, and disable attacking sites (they'd be pretty obvious:
> see the paper http://crypto.stanford.edu/~dabo/papers/ssl-timing.pdf for the
> classic explanation of one such attack -- there are a couple more) you
> should be safe for now.
Yup. I absolutely agree with this (and those attacks did make the "news"
too. :)
My issue is not the idea of a secure browser, but the claimed implementation
of one.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
