edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] FREAK
Date: Wed, 04 Mar 2015 09:10:59 -0800	[thread overview]
Message-ID: <87r3t47knw.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150204111907.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 04 Mar 2015 11:19:07 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> Has anyone looked into the freak attack
> as it relates to edbrowse and/or openssl?

Well, the freak attack site offers a client test.  Unfortunately, it is
too JS heavy for edbrowse.  I'm thinking this may be one of those deals
where if we're vulnerable, we just upgrade our libraries, and it'll be
fixed.

-- Chris

      reply	other threads:[~2015-03-04 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 16:19 Karl Dahlke
2015-03-04 17:10 ` Chris Brannon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r3t47knw.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).