From: hellekin <hellekin@gnu.org>
To: Guix <guix-devel@gnu.org>, Josh King <joshking@newamerica.net>,
JordiGH <jordigh@octave.org>
Cc: Zak Rogoff <zak@fsf.org>
Subject: GNU30 Security Hackathon
Date: Wed, 11 Sep 2013 10:16:20 -0300 [thread overview]
Message-ID: <52306D24.2020906@gnu.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
your project is part of the selection for the GNU30 hackathon listed
at http://www.gnu.org/gnu30/celebration
In the course of the anniversary, there's a security conference in
Buenos Aires, called Ekoparty, and I'm willing to organize a GNU
security hackathon there. [0]
Here is how it's supposed to work. Security hackers will be invited to
do one of the following things:
(1) Report zeroday vulnerabilities
(2) Fix security or privacy bugs
(3) Create, or give away security tools to the GNU project
My objective with this email is to gather a list of suggestions as to
where to put the effort on your various projects, in order to make it
more convenient for them to choose. I'm willing to gather
security-related bugs that they can look into and fix over a period of
3 days (obviously not full time), or ideas for useful tools related to
privacy or security.
Any suggestion welcome! Feel free to share this message in full or in
parts with your fellow hackers. The sooner I get answers, and the
better the participants can get ready and explore possibilities.
Regards, and happy hacking!
==
hk
[0] http://ekoparty.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCgAGBQJSMG0dAAoJEEgGw2P8GJg9rggP/0Gq5yQi61mz3/YiRYcEKzT0
geFlgVukY8IHA+CJkz3XkX8GcHBplCSxiRgRwCIwdfkamWWonzlU10sL2E9qfOcT
9lkmXHbUexh8YuJGGoTDqPbsuISCxfP7gtfPwvZGXtuf1jMQE75mrV1/qrcYZztt
LmDF6USqYZEDB7QKF82uVyYNuJuvmuhByXgCTsJp5Ac+vfsrsLAC+D+LmhNxoTOk
6fZghCUcglFWbMaMNbIudb0L+b43Zbhp7Cc9ZxDwb4xjeSUkHNbSg+YIDVac0/Hh
ac1UMAUuRMkFvPpWUPvvfh5Sp2YHF4jomVJn4jd+bKoOwIAiDn311KA4g6a7pkjz
XyTCxG6noyM3o5QmuHOpr5EBzM1qfqm2uzYoGmUz4OWrzdUixOuNz5y6AVrLvHiG
fA8jBveMrIwd1izohMpjnjXkfsn1dMt0qRdpyqEjjx8nnk1V7Ahw1auRdatSsDG7
DdAXrjG/8q1jCOH6GAgfElFPacQa0/Ms9v0DGXMkVU82SzCLmj4DhaX77ufSYF9T
5qCoskECq+0Ha8/Go278BKzM3S1DeRQHQfc3LNQyAccQzhz/6/YZycZ5FUfSiXLg
/WWYuxTD8wmLluQMShOVZzP8O9uukwRjIOQ34RRehn/FG1dQRmMH7rTtsRo4ag8h
HK7o2h1kEziCg7lsDGwZ
=yfnR
-----END PGP SIGNATURE-----
next reply other threads:[~2013-09-11 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 13:16 hellekin [this message]
2013-09-11 13:38 ` GNU30 Security Hackathon Jordi Gutiérrez Hermoso
2013-09-12 12:39 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52306D24.2020906@gnu.org \
--to=hellekin@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jordigh@octave.org \
--cc=joshking@newamerica.net \
--cc=zak@fsf.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).