Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] core infrastructure initiative
Date: Thu, 24 Apr 2014 11:54:15 -0400	[thread overview]
Message-ID: <0D912C71-957E-4ADD-B6A3-2ECA443A52EA@gmail.com> (raw)
In-Reply-To: <CAA93jw7zyMw5xVXq7Emp0wiXDisdw2ioYqYb8Ng4vwC=-nT46A@mail.gmail.com>

See also the LibreSSL effort, where they're hacking and slashing out ("flensing" - look it up) all the old cruft from OpenSSL to produce something less byzantine, more maintanable:

- http://www.libressl.org/ - their main site
- http://richb-hanover.com/libressl-fork-of-openssl/ - an excerpt of some snarky checkin comments from the effort above...

Rich

On Apr 24, 2014, at 11:44 AM, Dave Taht <dave.taht@gmail.com> wrote:

> http://arstechnica.com/information-technology/2014/04/tech-giants-chastened-by-heartbleed-finally-agree-to-fund-openssl/
> 
> The initiative came together quickly once the foundation began
> approaching the companies involved. “Before I could even get my last
> word out most folks were like, ‘absolutely,’” Zemlin said. “We should
> have done this three years ago to be honest.”
> 
> well, yea.
> 
> 
> -- 
> Dave Täht
> 
> NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


      reply	other threads:[~2014-04-24 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 15:44 Dave Taht
2014-04-24 15:54 ` Rich Brown [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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=0D912C71-957E-4ADD-B6A3-2ECA443A52EA@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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