[pm-h] Ideas for a July Meeting

[Todd Rinaldo]

I say we go with the original plan. Even at a security focused meeting, not
everybody may be interested in this. The value of the Hackathon is that
everybody can work on what they're interested in.

You should bring something with access to your code that you can run from
the meeting. Those interested will look at what you've got and talk about
your project. If others want to do something else, they can.

Todd

On Friday, June 21, 2013, Fraser Baker wrote:

> **
> Hi Todd:
>
> While not technically "hacking" I could present the probably naive
> measures I have take to secure various aspects of my application. Feedback
> would be greatly appreciated.
>
> However, postponing to another meeting based more on security might be
> more appropriate.
>
> Fraser
>
> ----- Original Message -----
> *From:* Mark Allen <javascript:_e({}, 'cvml', 'mrallen1 at yahoo.com');>
> *To:* Houston.pm located in Houston, TX. <javascript:_e({}, 'cvml',
> 'houston at pm.org');>
> *Sent:* Friday, June 21, 2013 12:28 PM
> *Subject:* Re: [pm-h] Ideas for a July Meeting
>
>  It'd be great to have @ cPanel, imo
>
>   ------------------------------
> *From:* Todd Rinaldo <todd at rinaldo.us>
> *To:* "Houston.pm located in Houston, TX." <houston at pm.org>
> *Sent:* Friday, June 21, 2013 11:59 AM
> *Subject:* Re: [pm-h] Ideas for a July Meeting
>
>  IMO, It's not technically cracking if it's your code. I think we could
> give some good advice to you on enhancing your security if that's your
> project you'd like help with. This is very much in line with a "Hack
> Session"
>
> If we're going to do a hacking session, I suggest we plan for 6-9. cPanel
> will provide the grub as usual. We can bypass the meet up in the lobby and
> simply ring the bell and/or call when you want in and we'll come get you.
> Alternatively we could meet somewhere public for this, but finding a good
> public wifi can be challenging.
>
>
> On Fri, Jun 21, 2013 at 11:51 AM, Fraser Baker <flbaker at sbcglobal.net>wrote:
>
> OK:
>
> My ignorance shows. Anyway, would a "Cracking" topic be of any interest?
>
> Fraser
>
> ----- Original Message ----- From: "Christopher Eades" <
> houstonpm at chromaxs.com>
> To: "Houston.pm located in Houston, TX." <houston at pm.org>
> Sent: Friday, June 21, 2013 11:06 AM
> Subject: Re: [pm-h] Ideas for a July Meeting
>
>
>
> What is being discussed is hacking in the traditional form: working on
> code with others.
>
> Attempting to break (into or otherwise) a website, or other software, is
> cracking.
>
> On 6/21/2013 11:08 AM, Fraser Baker wrote:
>
> Hi Todd:
>
> Look forward to learning more about Hacking. Perhaps I can participate
> by providing my website for hacking. It is probably pretty easy to hack,
> but if it is, I need to know how I can increase its security
>
> If interested, I'll provide its address.
>
> Fraser
>
>     ----- Original Message -----
>     *From:* Todd Rinaldo <mailto:todd at rinaldo.us>
>     *To:* Mark Allen <mailto:mrallen1 at yahoo.com> ; Houston.pm located in
>     Houston, TX. <mailto:houston at pm.org>
>     *Sent:* Thursday, June 20, 2013 12:29 AM
>     *Subject:* Re: [pm-h] Ideas for a July Meeting
>
>     I like the hack idea. I can come up with some CPAN projects that
>     could use some help or am happy to contribute if others need help.
>
>
>     On Wed, Jun 19, 2013 at 10:13 AM, Mark Allen <mrallen1 at yahoo.com
>     <mailto:mrallen1 at yahoo.com>> wrote:
>
>         Provided there's a venue, I would dig a technical session /
>         hack-a-thon deal.
>
>         Mark
>
>         ------------------------------**------------
>
> ------------------------------
>
> _______________________________________________
> Houston mailing list
> Houston at pm.org <javascript:_e({}, 'cvml', 'Houston at pm.org');>
> http://mail.pm.org/mailman/listinfo/houston
> Website: http://houston.pm.org/
>
>

-- 
Todd Rinaldo
todd at rinaldo.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/mailman/private/houston/attachments/20130622/c6dd1492/attachment.html>