Search results

This is all assuming there's actually a significant positive balance to hold.  Many of the skid hosts pretty much live 'week to week'.

Birds of a feather.

Passwords aside - that's a lot of names/emails/physical addresses that just got leaked.  Those folks won't be happy.

It's an old file, from back in the <4.* days.  I find it very hard to believe that they would take a secure, working file and replace it with such a massive security hole - so there's every reason to assume that all WHMCS versions are affected.

David's working on a fix now, from the hotel lobby.

The file in question is an old one, pre 4.* days.  I can't imagine they would replace a secure, working file with the atrocity there now, so safest just to assume all versions are affected.

Nah, go for it, I don't mind.

Yes, this is confirmed.  After seeing the... utterly incompetant coding practices, I wouldn't trust just using Maintenance mode.  I ripped down our entire install and just put up a placeholder for now.

http://localhost.re/p/whmcs-527-vulnerability tl;dr - A rather gaping security hole in WHMCS.  I've taken ours offline - strongly suggest other providers do the same.

True, but given that a CC "provider" likes to claim 'I've seen your racks, I know what you have'... I imagine hilarity would ensue if they tried to make an issue of whoever took that pic.  Hypocrisy always makes for the best drama.

http://www.reddit.com/r/SilkRoad/comments/1nl7p9/sr_shutdown_fallout_discussion/ And now I have this overwhelming urge to listen to Bobby Fuller.

My stance was always about preventing repeat offense.  New clients get the benefit of the doubt;  one of my primary goals was preventing someone that had been terminated for.. spam, for example, to stay on topic.. from just opening a new account and going at it again.  Our SBLs were a bit of a...

Ah, so it seems.  My apologies, looks like I was a bit out of the loop on this one.