@TheOutOfStarsException You should work for a pyromaniac

...you probably do already, now that I think about it; you just don't know.

It'd explain the explosions however.

lol

LyX is a ~800 MB install with its LaTeX dependencies

300 megs of that, however, is docs

@GeorgeEdison I love that the unicorn license is now copyrighted to you. Are you sure I'm not violating your copyright by using the license? ;-)

...docs of an optional LaTeX dependency

...docs of the extra part of an optional LaTeX dependency

@badpssockpuppet That makes them absolutely necessary!

@badpssockpuppet just use Word

I guess it's a way to punish people who install recommended packages without doublechecking

@KlausByskovHoffmann chat.stackexchange.com/rooms/176/…

I've had this discussion before :P

I'm going to bed, if you want to reply to messages in there ask somebody to unfreeze it for ya though :P

@badpssockpuppet Haha, no I don't think I have much to add to that ;-)

@ircmaxell - There? Need a bit o help with your class.

@KlausByskovHoffmann \o/

These days I'm getting to closely know the OOM Killer. Installing a 13 MB package killed Chromium.

Anyone here know PHP? @ircmaxell's class worked one way for me.

I can't decrypt my data!

@Moshe are you using the same salt to decrypt as you used to encrypt?

Yes

@KlausByskovHoffmann I am

I did this:

$e = new Encryption(MCRYPT_BlOWFISH, MCRYPT_MODE_CBC);

$key ="someCipherWhichI'veRedactedHere";

$filteredData['ccNumber'] = $e->encrypt($filteredData['ccNumber'], $key);
$filteredData['ccNumber'] = base64_encode($filteredData['ccNumber']);

@Moshe and what are you doing to decrypt?

hang on

		$ccnumber = $row['num'];

	$e = new Encryption(MCRYPT_BlOWFISH, MCRYPT_MODE_CBC);

	$dkey = "someCipherWhichI'veRedactedHere";

	$ccnumber = base64_encode($ccnumber);
	$ccnumber = $e->decrypt($ccnumber, $dkey);

@KlausByskovHoffmann - I've verified that cipher is the same.

er, hang on

You are base64 encoding twice

right, just noticed.

you should base64 decode before you decrypt

@KlausByskovHoffmann Fixing that didn't work.

)-:

Anyone got any ideas?

@KlausByskovHoffmann - The data is returned by base64_decode...

@Moshe, is that at least identical to the result of the initial encryption?

No idea.

check it

I didn't enter all the data

hang on

@badpssockpuppet hehe

@Moshe I will be back in about 10 minutes if you still need help

Thanks @TheOutOfStarsException, as always, of course I do ;-)

@JoshsSocks, it's laundry time!

Noooooo!

hahaha

@KlausByskovHoffmann - Could the DB be corrupting it?

@Moshe something must be corrupting it. A short test script should reveal what

Er, this is not good. seeing as I've already gotten several bits of info...

@KlausByskovHoffmann - How would you approach this?

There is info comming out of the DB

It's not letting me decrypt it.

I suspect the DB may be truncating it...

You have the code that puts things in the database right? and code that reads it out and tries to decrypt it?

Right

@KlausByskovHoffmann I do.

Just wrap your encryption logic in a function and your decyption logic in another function and make sure that following is true decrypt(encrypt(input)) == input

They are in two different scripts though...

I know, but you can copy/paste it into a test script, no?

I suppose.

(or refactor your code a little)

Ok, hang on...

Sup?

@ircmaxell - I've lost some info with your encryption script, apparently.

	$ccnumber = $row['num'];

	$e = new Encryption(MCRYPT_BlOWFISH, MCRYPT_MODE_CBC);

	$dkey = "someCipherWhichI'veRedactedHere";

	$ccnumber = base64_decode($ccnumber);
	$ccnumber = $e->decrypt($ccnumber, $dkey);

@ircmaxell Yes...

See the change, you need to use base64_decode there

see I changed it

I did change that.

didn't work.

The cipher is the same, honest.

@ircmaxell I already suggested that but apparently it does not work

Could varbinary(72) be truncating the encrypted data?

could

yes!

try changing it to 255

depends on the data

it shouldn't, since it's a CBC block cipher of size 8, so the encrypted data shouldn't be larger than 64 bytes assuming a 20 byte input

why are you storing base64 encoded data in a varbinary field?

It's a CC number, 16 character

@KlausByskovHoffmann @ircmaxell suggested it. What would you do?

store it in a plain varchar field or not base64 encode it at all

@KlausByskovHoffmann: because he was having trouble storing the raw in there

Duh!

it is cutting off

72 chars is the raw binary code

Oh dang.

bas64 will increase that by a factor of about 2

Oh man

no, 4/3

Thankfully that's only several "We shredded your CC number by mistake, please try again" emails.

PHP docs say about 33%

Always test!

@ircmaxell yes!

@ircmaxell Except when the supervisor is insisting that you have final build deployed yesterday.

@Moshe Doesn't matter!

I know.

@ircmaxell Ok, fair enough.

Always test. Especially when you're dealing with financial info

Long story.

@Moshe obviously not breaking something is more important than "releasing" on time