New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Granted, my understanding of copyright probably isn't all it should be, but how can they make that claim? It was just browsing the site while it was not under their control. Would that even stand up if you countered it?
Too late, @Asim posted first
Exactly!! and it does not even have a WHMCS logo in it, yes the hacker can claim copyright over it, LOL but not WHMCS
Youtube told me that they will update me in 14 days time, lets see
Apparently one of them has been arrested, http://news.softpedia.com/news/UGNazi-Hacker-Cosmo-Arrested-After-WHMCS-Breach-272565.shtml
Good.
One of them said you cant stop an idea, but thing is its a stupid idea to want to put 1000s of credit cards at risk.
You might want to read this article:
http://lifehacker.com/193343/ask-the-law-geek-is-publishing-screenshots-fair-use?tag=softwareaskthelawgeek
http://lifehacker.com/193343/ask-the-law-geek-is-publishing-screenshots-fair-use?tag=softwareaskthelawgeek
It wasn't a screenshot of WHMCS, but of the hacked version... so I don't think WHMCS can really claim ownership on it anyway...
I'm beginning to think that the whmcs hack was a real hack. Whmcs Just used the excuse that it was S.E. Logged a tix with HG as proof and blamed HG. Common, explain why when the database was leaked they were hacked the 2nd time. They are coders they def know how to change their own passwords. Explain the patch after the hack etc etc.
Coder isn't the same as smart.
Someone may have found an exploit in part of their site and not needed a password.
Someone may have decided now would be a good time to find an exploit, since they have a list of WHMCS installs; they may have found the source code somewhere and found an exploit; etc.
There are plenty of ways to explain all of this. And they're not even very far-fetched at all.
It's easy to upload and hide shells/exploits once you remote a box. Though granted, the WHMCS team should've done a -thorough- cleaning, or even a fresh start, after a compromise.
UGNazi took over MyBB.com but the MyBB.com Team got it back now.
I wonder if we have any updates on where this other Josh kid lives?
Finally my video has been restored and JoshTheGod aka "Mir Islam" has been arrested by FBI along with 23 others
http://www.asim.pk/2012/06/30/youtube-restored-my-video-finally/
Its digracefull whmcs even tried to get your video censored. Just shows what sorta company whmcs really is..
A responsible one for trying to protect their brand? :P
How are they protecting there brand? By censoring videos about the hacking. IMHO anyone who is still with whmcs is silly. Just asking to be attacked.
To err is a human, those who learn from it are Superman.
seriously, there scripts been fine for a pretty long time and still is. Hostbill is never going to get where whmcs is. Simply cause they are not stable( per price and support).
Whmcs has a huge Dev base and that itself is an A+ reason to why not to leave whmcs.
Explain. It wasn't WHMCS' fault for getting 'hacked' why would anyone leave them?
Running a whole website on a very unsecure server (yes, one) is not a fault?
A. How was the server insecure?
B. How does that translate to security hole in WHMCS?
HostGator.
So you are saying it was Hostgators fault.
Yes.
It was.
I know.
I used this point to disproove @giang.
Fuck WHMCS.
They would have been responsible if they admitted the breach, timely informed their users, and made a best effort to resolve the situation.
They didn't.
They didn't?
For hours on end, over 24 hours even, there was no word from WHMCS about the breach towards customers, other than an obscure blog post. A license reseller was faster in informing users by e-mail than WHMCS itself. After the breach, several other servers were breached and WHMCS acted as if nothing was going on, instead of - as they should have done - taking everything offline for a security audit.