Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • How many people used a recognizable word, or a name, or a word plus one or more digits; and how many used an (apparently) randomly generated password?
    • The problem is a bit worse than what the data implies. I won't speak for others, but quite some time ago, I received some email implying that someone was trying to get my password. Since I had been bad and reused a password, I immediately changed mine to a unique password. Now, I have a different password management system whereby I have unique, very hard to guess passwords for most critical sites.

      In the case of Perlmonks, I switched mine to pineappl. I really didn't care if that account got hacked and

  • I'd like to draw some attention to the analyzing script.

    Please notice how masak uses regexes and junctions of regexes as matchers, and doesn't need to distinguish them where he uses them.

    Also note that the use of the cross operator 'X' means that he has to use only one loop (instead of two nested loops).

    I really like that code. And I can't think of any Perl 6 feature (at least not off the top of my head) that would make that code even nicer, but is not yet implemented in Rakudo.

    • My reaction at seeing that code was something like horror - like seeing someone whose lips, nose, and eyelids have been cut off. Like you're talking to someone, and all you can think of is their bones underneath that will be left when they've died and rotted away. Surely that's not Perl. Surely!

      Will that feeling ever go away? :) I want it to seem awesome, too.

      • Um, I don't recall having such a reaction when reading Perl 6 code. But OTOH I learned it through the Apocalypses, so I only saw small pieces of it at a time.

        My advice to you is to write something in Perl 6 yourself, and then come back and report whether the feeling seems to subside, or at least lessen somewhat.

  • Just out of curiosity, is anyone with the list of passwords testing it against CPAN authors with the same or similar username or registered email address to make sure the passwords get changed? It seems like it'd be a good idea to regenerate the passwords or lock the accounts of people who don't change their password and have it published. Or, maybe someone should track their updates until they do.
    • I believe that they are emailing CPAN authors []

      (Luckly for me the last time I used PerlMonks I had forgotten my password so my password was set to the default forgotten password email's, but I still think I will go and change many of my passwords)

    • I tested the first few passwords that had email addresses. All of the people at the beginning of the list used their perlmonks password as their PAUSE password. After about three of these, I got depressed and stopped.
    • "the same or similar" is a hard test. Work is being done to try to identify any reused passwords (not limited to the published ones).
  • Who uses their good password for a discussion site, though? I can see if this was a list of online bank passwords how it'd be valuable, but honestly, if I could use a blank string as a password for these sites, I would. Who cares if someone posts a message "as me"?

    I liked larry's password the best, ">=6chars". (Presumably in response to a message like, "your password must be greater than or equal to 6 chars". Brilliant!)

  • Your script fails(!) to correctly analyze my old password (and at least one more), because it fails(!) to recognize whitespace. ;-)

    At least two passwords contained embedded whitespace. How many contained leading or trailing whitespace? IIRC, the source data was not formatted in a way that even preserved those, so who knows? :)

    perl -e 'print "Just another Perl ${\(trickster and hacker)},";'
    The Sidhekin proves that Sidhe did it!
    • You're completely right, I didn't take that into account. Nor do I see a way to do so, given the source data.

  • What significance is the strength of a compromised password? A password of "password" is no weaker than a password of "1a$3f&_j2^" if hackers compromise the system. Especially when the passwords are stored in plain text (WTF?)
    • I thought it would be interesting to do some analysis on the leaked passwords, that's all. We all have a pretty good idea of what makes for a strong password, and this was a chance to see how strong passwords some of the more high-profile Perl users out there were using. In that sense, the strength of compromised passwords is significant, because it gives us an unusual insight.

      I don't think I explained that clearly in the blog post. This was my way of generating a marginally useful blog post out of a negati