[Owasp-appsensor-project] [Owasp-appsensor-dev] GSoC 2016

Timo Goosen timo.goosen at owasp.org
Wed Mar 9 11:12:57 UTC 2016

Thanks glad if I could add something.

Good luck with GSOC.

I'm a bit busy but might have time next GSOC run to mentor.


On Tue, Mar 8, 2016 at 9:05 PM, John Melton <jtmelton at gmail.com> wrote:

> These are great - thanks Timo! I added them to the ideas page. Those could
> be a really useful output and are generic across applications - nice.
> On Tue, Mar 8, 2016 at 4:55 AM, Timo Goosen <timo.goosen at owasp.org> wrote:
>> My suggestions: (For reverse proxy)
>> Some checks related to cookies:
>> -Look at how many cookies a session has. There is a maximum between
>> browsers. We need to check between browsers I think the max is 255 or
>> something. The point of checking for more cookies than that is to prevent
>> cookie overflow.
>> -Look at how many characters a cookie contains.
>> -Some header related checks.
>> Regards.
>> Timo
>> On Thu, Mar 3, 2016 at 1:58 PM, Colin WATSON <colin.watson at owasp.org>
>> wrote:
>>> Fantastic news,
>>> Colin
>>> ---- John Melton wrote ----
>>> All,
>>> OWASP has been selected this year to participate in the Google Summer of
>>> Code! This is great news for the org, and hopefully appsensor will be able
>>> to participate again. We don't yet know how many slots we'll get, but now
>>> is the time to get started with planning. There are 2 specific things you
>>> can do:
>>> 1. If you are aware of students that might be interested, let them know
>>> ASAP. There's ~2 weeks for Q&A, then ~2 weeks for submission.
>>> 2. If you have time, sign up as a mentor. That could be for appsensor,
>>> or any of the other owasp projects. From past experience, I'd say you
>>> should plan for about 2-3 hours per week for the duration of the program
>>> (~3 months). It's a really good experience with smart students. It's an
>>> easy short-term way to contribute.
>>> Let me know if you have any questions.
>>> Thanks,
>>> John
>>> ----------------------------------
>>> Students will start applying for projects on March 14th but a lot of
>>> them are already exploring ideas on our corresponding wiki page:
>>> https://www.owasp.org/index.php/GSOC2016_Ideas.
>>> *How you can get involved:*
>>> If you are a project leader and would like for your project to
>>> participate add your idea on our  GSOC 2016 Idea
>>> <https://www.owasp.org/index.php/GSOC2016_Ideas> wiki page ASAP!
>>> *Become a Mentor:*
>>> Do you want to become a mentor for a student?
>>> Choose a participating OWASP project from the wiki page listed below preferably
>>> the one you are most familiar with.
>>> Link: https://www.owasp.org/index.php/GSOC2016_Ideas
>>> Touch base with the project leader and ask one of the org admins (
>>> Claudia <claudia.aviles-casanovas at owasp.org>, Kostas
>>> <konstantinos at owasp.org> or Fabio <fcerullo at owasp.org>) to send you an
>>> invitation and get you started today.
>>> *Help OWASP Invite Students: *
>>> Are you somehow affiliated with a university? Get in touch with
>>> students, inform them about the program and how they can participate with
>>> OWASP.  Please direct students to the wiki page for details:
>>> https://www.owasp.org/index.php/GSoC
>>> Please let us know if you need help or supporting material.
>>> Thank you in advance for your time and look forward to your
>>> participation.
>>> _______________________________________________
>>> Owasp-appsensor-project mailing list
>>> Owasp-appsensor-project at lists.owasp.org
>>> https://lists.owasp.org/mailman/listinfo/owasp-appsensor-project
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-appsensor-project/attachments/20160309/d1335e04/attachment.html>

More information about the Owasp-appsensor-project mailing list