Search results

I can't stop hearing "Huge... tracts of land" now <_< 

Ahahahaha, bloody hell.  A node with 300GB of "physical" RAM?  Must be one hell of a chassis :P

Sorry sir, I don't have the DB.  I'm sure it'll turn up eventually though.

@ Welp... wasn't originally gonna say anything.  But I have a new query for those of you that were curious about his claims that "there was no more oversell". SELECT nodes.nodeid, nodes.name, COUNT(vservers.vserverid) as vservers, SUM(vservers.ram)/1073741824 AS ram FROM nodes, vservers WHERE...

There's a reason I chose to use my full name here (and WHT) as opposed to just 'Aldryic'.

I agree fully. And while I doubt we'll do the pubkey offload, what we're planning on doing with Stallion2 is setting a random root pass on the node, and not sending it via email/etc. The New VPS email will simply instruct the client to login, set a root pass for the VM, and then continue use...

Never was a fan of replacing one line of code with... 28. All you're needing is a random alphanumeric, which PHP cannot easily provide (And then you have to screw with php blocks in smarty, never fun). Generating a random number, then md5/SHA'ing that to 'randomize' it further with...

Nah, by all means go for it :P I wouldn't have posted it publicly if I didn't want folks to use it :3 General rule for my code is - if I post it publicly, anyone can use it as they see fit.

He means that the source of the claim is untrustworthy, and should not be taken at face value just because of the situation at hand.

We generate a random, uneditable password when any order is placed, correct. Primarily to force clients to set a new root password themselves afterward (unless they actually want to remember a random string &lt;_&lt;) as a security precaution. That's not a module/etc setting though - just a...

Root passes are viewable? O_o That is straight-up disastrous - they're either storing root passes in plaintext, or merely displaying the WHMCS 'password' field (also plaintext), which is absolutely useless after running `passwd` on the VM (like people should be doing).

Hah, nice. Looks like they've made some major improvements (as far as options, at least) on the module. Only reference I had was the module we worked with a couple years back that just threw this big nasty blob into the client area; no ability to enable/disable certain features.

Does the SolusVM WHMCS plugin allow changes to rootpass/hostname/etc? If so, you may want to try and disable that, just in case they're not sanitizing input <_<

&amp;nbsp; That's perfect, thanks. He only made one attempt? Edit, Unrelated: I guess I'm gonna have to break down and start using a 'proper' browser... links is butchering the hell out of the BBCode and quote attempts <_<

If you would, make a text file of Robert's attempts to try it against you, please. I'm putting together similar information for Nick, as I believe he's going to pursue a criminal case on this. (You also might want to grep your logs for the googlecode bit I mentioned before).

Assuming he didn't do the actual hit to begin with.  On a more amusing note, someone has been trying to use the http://code.google.com/p/slowhttptest/ tool from a couple different VPSes (I'll be emailing the providers shortly) to try and slam the exploit link with us.  Stallion doesn't have this...

His affiliation with the LulzSec group (and other unsavories), to put it shortly.  From http://www.guardian.co.uk/technology/2011/jun/24/lulzsec-irc-leak-the-full-record : I tend to take issue with someone actively trying to turn negative attention towards our network.  There are other reasons...

  Pretty much the only sensible move the kid has made.  joepie and his ilk are exactly the sort you _avoid_ if you're trying to run a legitimate business.

There's no doubt at all that Robert Clarke (the real kid, not the imposter(s)) was the one that attempted to run the exploit on us as well.  By his own admission (visible in his Twitter timeline, until he locked his account from public view a few minutes ago) he was "testing a bunch of...

His service with us was ended due to an unrelated matter.  Privacy policy prevents me from going any more into detail on that.. but it had nothing to do with this :P