| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
Comments:
<0> *shrug*; it's your time.
<1> litage: Pretty much what I said yesterday. MD5-crypt is designed to be slow and heavy ;)
<2> dondelelcaro: that it is :-/
<2> litage: I like Digest::SHA's SHA-512 abilities
<2> never tested them for speed though, but I think it uses underlying C to do the dirty work
<1> litage: there's no way to check a hash without doing quite a considerable amount of math, which strengthens it against brute forcing
<3> alright i think i figured it out
<0> or the nicely confusing 06/02/2005 03:50:00 AM
<4> wtf?
<4> oh, sorry, wrong window
<5> why would a CGI script be sending a HTTP/1.1 200 OK before i get to send my header?
<5> ok, so what's the difference between an array and a list
<5> [hint] shift knows it
<6> f00li5h: @array, ('i', 'am', 'a', 'list');
<7> an array is a variable. a list is an abstract
<5> imMute: so you ***ign a list to an array?
<8> imMute: Not really.
<5> this, is , a , list
<8> f00li5h: Not really.
<5> @{[this, is , an , array ]}
<9> confusor.
<8> f00li5h: Again, not really.
<5> buu: do tell!
<7> a list is not tangible
<8> f00li5h: It's a little complicated.
<1> It's similar to the difference between a scalar and a literal string. An array is a variable you can muck with. A list is just a list.
<8> But basically, yeah
<1> But the value of an array (in list context, of course) is a list
<8> A list is an abstract concept created by perl
<5> buu: i've got the rest of today, and then 2 dyas of weekend
<8> Not somethign your code does.
<8> eval: @{[this, is , an , array ]}
<10> buu: Return: 4
<6> a list is something people use to sort out the perl noobs
<8> Hrm, actually, I was thinking of a hash slice there..
<9> imMute: right, they have no practical application outside of that
<8> f00li5h: I take it back, @{} is mostly an array =]
<5> buu: ^_^
<7> mrm.. @{} coerces an array?
<1> buu: of course it is. It's spelled with an @
<8> pravus: Dereferences
<5> pravus: yes, but when evaluated, it's an array
<8> hobbs: Yeah, except for the things spelled with @ that aren't..
<5> pravus: it's schrodingers array
<1> buu: mmm, true. Slices, you mean?
<8> eval: @{ {qw/a b c d e f h/} }{ qw/c d e/ }
<10> buu: Return: f
<7> schrodinger doesn't exist... or does he?
<5> pravus: i'll have a look for you.
<5> pravus: well, it looks like he's dead anyway...
<11> buu, what happened there?
<8> bluebeard: comma operator in scalar context.
<11> interesting
<11> perldoc perllol?
<10> perllol - Perl data structures: arrays of arrays. To access this perldoc please type, at a command line, 'perldoc perllol'. You may also find it at http://perldoc.perl.org/perllol.html
<1> bluebeard: produces the list qw(d '' f), and the bot imposes scalar context, so you get the last value :)
<8> I forget where that one is documented.
<1> more or less
<8> but @x{1,2,3} turns in to $x{1},$x{2},$x{3}
<1> eval: qw(a b c)
<10> hobbs: Return: c
<12> hobbs: how does crypt-md5 compare to hmac-md5?
<8> (qw//, also produces a comma seperated list)
<8> (commas,they rock)
<5> buu: argh
<11> ahh
<5> buu: so a list is just somwhere that an array can be an array
<5> right?
<1> litage: don't know personally, but HMAC-MD5 seems to be well-respected enough. And there's an HMAC-SHA1
<11> eval: (a,b,c)
<10> bluebeard: Return: c
<11> why does it return c
<11> ?
<1> bluebeard: because the comma operator in scalar context acts like the "C comma"
<12> can anyone else comment on the differences between crypt and hmac?
<1> bluebeard: evaluates its left operand, evaluates its right operand, and returns the value of the right one
<5> litage: not i
<1> litage: the HMAC is designed to authenticate that a given message was produced by someone with access to a given secret key (and is verified by that same key)
<1> litage: MD5 crypt is in essence "just a hash" -- it's just a wickedly modified version of the MD5 algorithm
<11> eval: $x='a'; (hex($x), $x+1);
<10> bluebeard: Return: 1
<13> eval: [a,b,c]
<10> Teratogen: Return: ['a','b','c']
<11> eval: $x='a'; $x+1;
<10> bluebeard: Return: 1
<11> awww
<13> eval: { a->a, b->b, c->c }
<10> Teratogen: Error: Can't locate object method "a" via package "a" (perhaps you forgot to load "a"?) at (eval 186) line 1.
<11> you can't add to an integer, that's sad.
<13> eval { a=>a, b=>b, c=>c }
<13> oops
<1> eval: $x = 42; $x++, $x*2;
<10> hobbs: Return: 86
<13> eval: { a=>a, b=>b, c=>c }
<10> Teratogen: Return: {'c' => 'c','a' => 'a','b' => 'b'}
<1> bluebeard: follow?
<12> hobbs: if i have access to crypt-md5 and hmac-md5, shall i use hmac?
<1> litage: depends? Do you need a p***word hash or do you need an HMAC?
<13> eval: sort(keys({a=>a,b=>b,c=>c}))
<10> Teratogen: Error: Type of arg 1 to keys must be hash (not single ref constructor) at (eval 186) line 1, near "})"
<13> hm
<1> bluebeard: you can use it to sequence operations, like a semicolon does -- except that it's valid where an _expression_ is expected, instead of a statement :)
<13> eval: sort(keys(%{a=>a,b=>b,c=>c}))
<1> eval: sort keys %{ {a=>a, b=>b, c=>c} }
<10> Teratogen: Error: syntax error at (eval 186) line 1, near "%{"
<10> hobbs: Return:
<13> =)
<13> darn!
<12> hobbs: i need to store encrypted/encoded/etc p***words
<14> %{${}}
<14> %{${a=>b, b=>c}}
<13> eval: %foo={a=>a,b=>b,c=>c}; return(sort(keys(%foo));
<10> Teratogen: Error: syntax error at (eval 186) line 1, at EOF
<13> ah
<5> litage: where are you storing them?
<14> return?
<12> f00li5h: in a database
<14> print sort keys %foo;
<13> eval: %foo={a=>a,b=>b,c=>c}; print sort keys %foo;
<10> Teratogen: HASH(0x843b4bc)Return: 1
<1> litage: for what purpose?
<5> litage: why not just use the md5 function that came with your db?
<1> litage: authenticating against them?
<13> bah
<1> eval: $^W=1; %foo={a=>a,b=>b,c=>c};
<10> hobbs: Reference found where even-sized list expected at (eval 186) line 1. Return: 1
<13> enough buufrivolity
<12> hobbs: yes, authenticating against them
<1> litage: then you don't want an HMAC
<11> man it ****s being a loser
<12> f00li5h: i'm pretty sure the md5 function that comes with my db isn't as secure as crypt-md5
<9> bluebeard: i wouldn't know!
<12> hobbs: why is that? i've only started reading up on HMAC, so i don't fully understand it yet
<5> litage: secure? it's md5, they're all the same...
<1> <1> litage: the HMAC is designed to authenticate that a given message was produced by someone with access to a given secret key (and is verified by that same key)
<12> f00li5h: i've just learned that crypt-md5 is different from md5
<12> hobbs: would the message not be the p***word?
<1> litage: it wouldn't
<1> litage: that would require storing the p***words in the clear, among other things ;)
<5> litage: the message is sent along with a cryptogram
<11> my friend that I've had a crush on, and thought liked me is now dating her peircer.
<14> perl -le '%foo = ( 1 => a, 3=>c, 2=>b ); print sort keys %foo;'
<5> litage: then the person that receives the message, can check the cryptogram against the message and the sender's public key
<1> f00li5h: not "public key". That's the difference between HMACs and signatures.
<11> either I'm a nice guy and chicks don't notice me, or I'm an *** and they don't wanna talk to me.
<1> f00li5h: HMACs are symmetric systems. There's _one_ key, not a keypair.
<5> hobbs: right, sorry.
<12> hobbs: the user wanting to be authenticated would supply the plaintext p***word
<1> litage: and? :)
Return to
#perl
or
Go to some related
logs:
#php
install glibc ubuntu
how to install frostwire - ubuntu
send email from php with diferent account of nobody
#suse
#linux
hpet xorg
#math
#css
odin_ fatal error
|
|