From bradley.d.andersen at gmail.com Thu Mar 1 13:03:51 2012 From: bradley.d.andersen at gmail.com (Bradley Andersen) Date: Thu, 1 Mar 2012 16:03:51 -0500 Subject: [Purdue-pm] Book? Message-ID: Anyone read this: Print ISBN:978-1-4493-1428-6 ISBN 10:1-4493-1428-7 ?? If so, would you recommend it? If not, will you recommend something along that vein? Thanks! Brad Andersen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jacoby at purdue.edu Thu Mar 1 13:35:12 2012 From: jacoby at purdue.edu (Dave Jacoby) Date: Thu, 01 Mar 2012 16:35:12 -0500 Subject: [Purdue-pm] Book? In-Reply-To: References: Message-ID: <4F4FEB90.1000104@purdue.edu> On 3/1/2012 4:03 PM, Bradley Andersen wrote: > Anyone read this: > > Print ISBN: > 978-1-4493-1428-6 > ISBN 10: > 1-4493-1428-7 > > ?? > Sorry. I've looked through 0-596-00789-2 a little, and a few chapters of 978-1-4493-1640-2 and 978-0-596-52708-2. I don't really have much call for that extra mile, yet. -- Dave Jacoby Address: WSLR S049 Code Maker Mail: jacoby at purdue.edu Purdue University Phone: 765.49.67368 767 days until the end of XP support From bradley.d.andersen at gmail.com Thu Mar 1 18:20:12 2012 From: bradley.d.andersen at gmail.com (Bradley Andersen) Date: Thu, 1 Mar 2012 21:20:12 -0500 Subject: [Purdue-pm] Book? In-Reply-To: <4F4FEB90.1000104@purdue.edu> References: <4F4FEB90.1000104@purdue.edu> Message-ID: Bonus points for responding to numbers with numbers :) On Thu, Mar 1, 2012 at 4:35 PM, Dave Jacoby wrote: > On 3/1/2012 4:03 PM, Bradley Andersen wrote: > >> Anyone read this: >> >> Print ISBN: >> 978-1-4493-1428-6 >> ISBN 10: >> 1-4493-1428-7 >> >> ?? >> >> > Sorry. I've looked through 0-596-00789-2 a little, and a few chapters of > 978-1-4493-1640-2 and 978-0-596-52708-2. I don't really have much call for > that extra mile, yet. > > -- > Dave Jacoby Address: WSLR S049 > Code Maker Mail: jacoby at purdue.edu > Purdue University Phone: 765.49.67368 > 767 days until the end of XP support > > > ______________________________**_________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/**listinfo/purdue-pm > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikeb at purdue.edu Fri Mar 2 05:06:09 2012 From: mikeb at purdue.edu (Mike Budzik) Date: Fri, 2 Mar 2012 08:06:09 -0500 (EST) Subject: [Purdue-pm] Book? In-Reply-To: Message-ID: <441313723.330222.1330693569589.JavaMail.root@mailhub019.itcs.purdue.edu> I read the 2004 edition (several years ago). It was written with MySQL 4.0 in mind. There are a couple of parts in the book that talk about MySQL 4.1 and 5.0, which were in alpha or maybe beta at the time. If you are comfortable with MySQL, but really want to get past the basics and start considering things like which storage engine is best for a particular situation or how to make sure you are getting (and keep getting) good performance, then the book is good. Mike B From: "Bradley Andersen" To: "Dave Jacoby" Cc: purdue-pm at pm.org Sent: Thursday, March 1, 2012 9:20:12 PM Subject: Re: [Purdue-pm] Book? Bonus points for responding to numbers with numbers :) On Thu, Mar 1, 2012 at 4:35 PM, Dave Jacoby < jacoby at purdue.edu > wrote: On 3/1/2012 4:03 PM, Bradley Andersen wrote: Anyone read this: Print ISBN: 978-1-4493-1428-6 ISBN 10: 1-4493-1428-7 ?? Sorry. I've looked through 0-596-00789-2 a little, and a few chapters of 978-1-4493-1640-2 and 978-0-596-52708-2. I don't really have much call for that extra mile, yet. -- Dave Jacoby Address: WSLR S049 Code Maker Mail: jacoby at purdue.edu Purdue University Phone: 765.49.67368 767 days until the end of XP support ______________________________ _________________ Purdue-pm mailing list Purdue-pm at pm.org http://mail.pm.org/mailman/ listinfo/purdue-pm _______________________________________________ Purdue-pm mailing list Purdue-pm at pm.org http://mail.pm.org/mailman/listinfo/purdue-pm -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at purdue.edu Fri Mar 2 11:58:48 2012 From: mark at purdue.edu (Mark Senn) Date: Fri, 02 Mar 2012 14:58:48 -0500 Subject: [Purdue-pm] free _Programming Perl_ 3rd edition Message-ID: <8607.1330718328@pier.ecn.purdue.edu> To get a free _Programming Perl_, 3rd edition (the fourth edition is out now) tree-book be the first to answer this email. -mark From mark at ecn.purdue.edu Fri Mar 2 12:12:19 2012 From: mark at ecn.purdue.edu (Mark Senn) Date: Fri, 02 Mar 2012 15:12:19 -0500 Subject: [Purdue-pm] free _Programming Perl_ 3rd edition In-Reply-To: <8607.1330718328@pier.ecn.purdue.edu> References: <8607.1330718328@pier.ecn.purdue.edu> Message-ID: <13379.1330719139@pier.ecn.purdue.edu> The book has been claimed. -mark From jacoby at purdue.edu Fri Mar 16 08:28:55 2012 From: jacoby at purdue.edu (Dave Jacoby) Date: Fri, 16 Mar 2012 11:28:55 -0400 Subject: [Purdue-pm] Upcoming Meeting: Tuesday, March 20 Message-ID: <4F635C37.9060106@purdue.edu> Next Tuesday is the next meeting, at the same Perl time (11:30-1) and the same Perl channel (WSLR 116). On the schedule is me, going on about how I automated flow onto the Purdue Perl Mongers twitter feed, @purduepm, with possible talks from Mark on Perl6 Infix operators or controlling a robot chassis with Perl 5. If you have a talk idea, preferably Perl-related but not necessarily, please tell the list or put it on the PPM wiki page. Maybe I should write a list notifier using Template Toolkit and Email::Simple, then present it. Or, maybe someone else can.... http://pm.purdue.org/Wiki/wiki.pl/UpcomingMeetings -- Dave Jacoby Code Maker, Purdue Genomics Core Lab http://web.ics.purdue.edu/~djacoby 752 days until the end of XP support From jacoby at purdue.edu Mon Mar 19 12:12:57 2012 From: jacoby at purdue.edu (Dave Jacoby) Date: Mon, 19 Mar 2012 15:12:57 -0400 Subject: [Purdue-pm] Tomorrow is Perl Mongers! Message-ID: <4F678539.4090109@purdue.edu> Just mailing a reminder that Perl Mongers meets tomorrow in WSLR 116. Right now, There three scheduled talks: Tweeting about Perl with Perl, by me Defining your own Infix Operators using Rakudo implementation of Perl 6, by Mark Senn Hardware Misadventures (or, Why using the Web is so Frustrating), by Mark Senn See you tomorrow! -- Dave Jacoby Code Maker, Purdue Genomics Core Lab http://web.ics.purdue.edu/~djacoby 749 days until the end of XP support From jacoby at purdue.edu Fri Mar 23 07:25:16 2012 From: jacoby at purdue.edu (Dave Jacoby) Date: Fri, 23 Mar 2012 10:25:16 -0400 Subject: [Purdue-pm] Richard Stallman of the FSF @ Purdue March 29 Message-ID: <4F6C87CC.4000608@purdue.edu> Richard Stallman will be talking on invite from Nanohub at 4:30 on March 29 in ME 1130. He is a somewhat controversial figure, sure, but without the GNU Project, without gcc and the GPL, much of what we rely on as Perl programmers would not exist. Hope to see you there. https://calendar.purdue.edu/Calendar/EventList.aspx?fromdate=3%2F21%2F2012&todate=3%2F30%2F2012&display=Day&type=public&eventidn=62263&view=EventDetails&information_id=123472 -- Dave Jacoby Code Maker, Purdue Genomics Core Lab http://web.ics.purdue.edu/~djacoby 745 days until the end of XP support From bradley.d.andersen at gmail.com Fri Mar 23 08:57:15 2012 From: bradley.d.andersen at gmail.com (Bradley Andersen) Date: Fri, 23 Mar 2012 11:57:15 -0400 Subject: [Purdue-pm] Richard Stallman of the FSF @ Purdue March 29 In-Reply-To: <4F6C87CC.4000608@purdue.edu> References: <4F6C87CC.4000608@purdue.edu> Message-ID: Well, he's sort of a hypocrite, but, aren't we all? :) I would like to hear him speak, but I may be cringing the whole time. On Fri, Mar 23, 2012 at 10:25 AM, Dave Jacoby wrote: > Richard Stallman will be talking on invite from Nanohub at 4:30 on March > 29 in ME 1130. He is a somewhat controversial figure, sure, but without the > GNU Project, without gcc and the GPL, much of what we rely on as Perl > programmers would not exist. > > Hope to see you there. > > https://calendar.purdue.edu/**Calendar/EventList.aspx?** > fromdate=3%2F21%2F2012&todate=**3%2F30%2F2012&display=Day&** > type=public&eventidn=62263&**view=EventDetails&information_**id=123472 > -- > Dave Jacoby > Code Maker, Purdue Genomics Core Lab > http://web.ics.purdue.edu/~**djacoby > 745 days until the end of XP support > > ______________________________**_________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/**listinfo/purdue-pm > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bradley.d.andersen at gmail.com Fri Mar 23 12:40:55 2012 From: bradley.d.andersen at gmail.com (Bradley Andersen) Date: Fri, 23 Mar 2012 15:40:55 -0400 Subject: [Purdue-pm] Mobile + Perl Message-ID: I am needing to add mobile support (version?) to a very complicated CGI::* site. Any general hints? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jacoby at purdue.edu Fri Mar 23 13:11:06 2012 From: jacoby at purdue.edu (Dave Jacoby) Date: Fri, 23 Mar 2012 16:11:06 -0400 Subject: [Purdue-pm] Mobile + Perl In-Reply-To: References: Message-ID: <4F6CD8DA.2010905@purdue.edu> On 3/23/2012 3:40 PM, Bradley Andersen wrote: > I am needing to add mobile support (version?) to a very complicated > CGI::* site. Any general hints? My suggestions: 1) know what you want the site to do, both in mobile and in general, and what can be held back 2) have each block have a class or ID that you can access with CSS 3) using media queries, only display the essentials once a page is down to hide the less essential parts -- Dave Jacoby Code Maker, Purdue Genomics Core Lab http://web.ics.purdue.edu/~djacoby 745 days until the end of XP support From gizmo at purdue.edu Fri Mar 23 13:27:26 2012 From: gizmo at purdue.edu (Joe Kline) Date: Fri, 23 Mar 2012 16:27:26 -0400 Subject: [Purdue-pm] Mobile + Perl In-Reply-To: References: Message-ID: <4F6CDCAE.8050808@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/23/2012 03:40 PM, Bradley Andersen wrote: > I am needing to add mobile support (version?) to a very complicated > CGI::* site. Any general hints? Look at Twitter's bootstrap for the css. It basically gives you a responsive site for free. That is assuming your html markup and such amenable to such css changes. Take a look at: http://blogs.perl.org/users/joel_berger/2012/03/mojolicious-bootstrap-awesome.html He doesn't go into much detail but he based his site on mojolicious but CGI is really just the backend. Your html/css/javascript is what really makes a site mobile friendly. joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9s3K0ACgkQb0mzA2gRTpnbtgCdHpJPN08Ikw3doRkFlII9+DHF 1KkAnRHe39sJ5NT7t1nEJLoyQV4PWaxx =XFZi -----END PGP SIGNATURE----- From bradley.d.andersen at gmail.com Sat Mar 31 11:33:55 2012 From: bradley.d.andersen at gmail.com (Bradley Andersen) Date: Sat, 31 Mar 2012 14:33:55 -0400 Subject: [Purdue-pm] TripleDES In-Reply-To: References: Message-ID: got any experience with this? I don't. If you do, here's an encrypted string and the key (base 64): RL5ZJUYNxNMnqa9wusptOSuDRAgIJ+mJ (string) L1uu9NwccM0TJWTmUj2heiO/WHMl7wKP (key) Can you tell me the original string? perl doesn't seem to have good 3des ... or i'm stupid. From djacoby at purdue.edu Sat Mar 31 16:37:44 2012 From: djacoby at purdue.edu (David A Jacoby) Date: Sat, 31 Mar 2012 19:37:44 -0400 (EDT) Subject: [Purdue-pm] TripleDES Message-ID: <717F00A2-D76A-4457-A1E9-54FB6FAF836A@purdue.edu> Will look into it soon. But isn't 3DES broken? -- Dave Jacoby jacoby at purdue.edu Not at his desk ----- Reply message ----- From: "Bradley Andersen" Date: Sat, Mar 31, 2012 2:34 pm Subject: [Purdue-pm] TripleDES To: "Purdue Perl Mongers" got any experience with this? I don't. If you do, here's an encrypted string and the key (base 64): RL5ZJUYNxNMnqa9wusptOSuDRAgIJ+mJ (string) L1uu9NwccM0TJWTmUj2heiO/WHMl7wKP (key) Can you tell me the original string? perl doesn't seem to have good 3des ... or i'm stupid. _______________________________________________ Purdue-pm mailing list Purdue-pm at pm.org http://mail.pm.org/mailman/listinfo/purdue-pm From mark at ecn.purdue.edu Sat Mar 31 20:16:41 2012 From: mark at ecn.purdue.edu (Mark Senn) Date: Sat, 31 Mar 2012 23:16:41 -0400 Subject: [Purdue-pm] TripleDES In-Reply-To: References: Message-ID: <14818.1333250201@pier.ecn.purdue.edu> Bradley Andersen wrote: > If you do, here's an encrypted string and the key (base 64): > RL5ZJUYNxNMnqa9wusptOSuDRAgIJ+mJ (string) > L1uu9NwccM0TJWTmUj2heiO/WHMl7wKP (key) SUMMARY---USE THIS CODE TO DECODE IT Use this code to decode it. Perl may have something better that handles the three parts of the key bundle behind the scenes but I think this may work like you want. #!/usr/bin/perl use strict; use warnings; use Crypt::DES; use MIME::Base64::Perl; use feature 'say'; my $string64 = 'RL5ZJUYNxNMnqa9wusptOSuDRAgIJ+mJ'; my $key64 = 'L1uu9NwccM0TJWTmUj2heiO/WHMl7wKP'; my $string = decode_base64($string64); my $key = decode_base64($key64); my $key1 = substr $key, 0, 8; my $key2 = substr $key, 8, 8; my $key3 = substr $key, 16, 8; my $cipher1 = new Crypt::DES $key1; my $cipher2 = new Crypt::DES $key2; my $cipher3 = new Crypt::DES $key3; my $output = ''; while (length $string) { my $t = substr $string, 0, 8; $output .= $cipher1->decrypt($cipher2->encrypt($cipher3->decrypt($t))); $string = substr $string, 8; } say $output; DETAILS---MISCELLANEOUS MUSINGS---SKIP UNLESS YOU'RE REAALLY INTERESTED >From http://csrc.nist.gov/groups/STM/cavp/documents/des/tripledesval.html Notice: The DES Transition Plan has ended as of May 19, 2007. The DES Transition Plan addresses the use of single key DES by Federal agencies, which are incorporated in cryptographic algorithms. Therefore Triple DES Keying Option 3 (Key1 = Key2 = Key3) is no longer Approved. >From reading I've done it looks like single and double DES are no longer recommended but triple DES is still used. The key is 32 characters long and each character is base 64 encoded so there are 32 * 6 = 192 bits in the key. According to http://en.wikipedia.org/wiki/Triple_DES#Keying_options Triple DES uses a "key bundle" which comprises three DES keys, K1, K2 and K3, each of 56 bits (excluding parity bits). The encryption algorithm is: ciphertext = EK3(DK2(EK1(plaintext))) I.e., DES encrypt with K1, DES decrypt with K2, then DES encrypt with K3. Continuing with http://en.wikipedia.org/wiki/Triple_DES#Keying_options Decryption is the reverse: plaintext = DK1(EK2(DK3(ciphertext))) I.e., decrypt with K3, encrypt with K2, then decrypt with K1. See http://www.cryptosys.net/3des.html for instructions of how to extract K1, K2 and K3 from the 192 bits in the key bundle. Once you've got K1, K2, and K3 you may want to try using MIME::Base64::Perl to do the plaintext = DK1(EK2(DK3(ciphertext))) -mark