> "This was a sophisticated cyber-attack on our company which we are still investigating."
Ah, so the database was stored in an unsecured Amazon bucket then. Got it.
335 posts • joined 24 Feb 2008
The entire download archive was mirrored by archive.org a few years ago, so you don't have to resort to downloading unsigned executables from totallylegitdrivers.ru for all your driver needs:
Jason Scott, of the Internet Archive, is working to ensure that that mirror is current before Intel makes it go away forever:
"What about the other European armies?"
"Oh they're alright, on weekdays anyway."
"The Dutch, Danish and Belgian armies go home on the weekends."
"So if the Russians are going to invade we'd prefer them to do it between Monday and Friday. Is this widely known?"
"Well if I know it I'm sure the Russians do. The Kremlin always gets NATO defence secrets before they filter down to us at Number 10."
It was actually found weeks ago and spread around the Apple developer forums. By the time it went big yesterday it was already well known to a large group of people. This wasn't a case of a careless security researcher dropping a zero-day publicly because he didn't feel like reporting it, it was a developer who wasn't aware of the full impact of a bug complaining that Apple had not even acknowledged that it existed let alone discussed the possibility of a fix.
Was this the best way to handle the issue? Nah, not really. But is it "right" for one of the many people who discussed this issue publicly to be crucified for doing so, as you suggest? No, not that either.
Also if you read the technical details, the "root account without a password" already was eliminated from the auth DB and should have been completely inaccessible. The root of the problem was that the authentication code wrongly decided that it was time to enable the disabled account by creating it anew, with the (blank) password which had been provided by the user.
Sadly, things are never quite as simple as they look.
But the problem with that is, regular people aren't allowed access to that software unless they're a LEA or popular service like Facebook. (Which sucks, as I have a large anime artwork collection I'd love to sort through far more easily to remove duplicates.)
This isn't a BYOD solution. It doesnt solve the issues discussed (laptops, desktops, macbooks etc).
Did you read the article?
I thought you knew. The comments section switched to a Bring Your Own Article policy several months ago. It adds a little bit of administrative overhead and may have some minor impact on the coherency of comments, but we feel that it makes the users happier in the long run.
"So a "ding dong" is a warning signal of visitor, post, or circular. If followed by a Westminster chime then it means someone is ringing the bell."
And if it is followed closely by the sound of barking dogs and screaming then the bell has been rung by a door-to-door soul saver, utilities fraud team or a salesperson from Citrix.
"There is something a little off with this."
There sure is. I think you should look at changing the vendor you purchase domain names from, as it really shouldn't take "a few hours minimum" to sign in to a control panel, type or paste in a domain name, check the box that says "Yes please put this domain on the same domain name servers I always use" and then push a button to buy it. It's a five minute job at most, and that includes typing your password wrong four times and swearing a bit before you turn Caps Lock back off. And if you're concerned about the cost, which is less than the price of buying warm drinks for the entire team one time, you can typically 'return' the domain a few days later and end up paying nothing.
What you may be missing is that checking in with a mysteriously named domain is a fairly common technique for malware to use, and that it is not unusual to take control of expired, unregistered or cancelled domains to 'sinkhole' them, effectively shutting down an entire botnet by not only removing its central command and control facility but also redirecting the C&C traffic to a friendly site where you can keeps tabs on botnet infections and activity. The value isn't just in stopping a single infection on your local network, but also in seeing what every other infected host in the world is doing, so taking a few minutes to register a domain and point it to your existing sinkhole server is a reasonable thing to do.
This is exactly what MalwareTech described in his original write-up of WannaCrypt ( https://www.malwaretech.com/2017/05/how-to-accidentally-stop-a-global-cyber-attacks.html ), and he includes some data he was able to collect on global and regional infection rates through the sinkholed domain.
It may seem odd if you're not familiar with modern botnet hunting, but what MalwareTech did wasn't that unusual.
What you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.
"There's never been a period that I've NOT heard SCSI pronounced that way."
When Larry Boucher invented SCSI he wanted it to be pronounced "Sek-see". Everyone else on the committee thought that sounded unprofessional and decided it should be "Scuh-zee" instead.
I'm pretty sure that this was the same group which later renamed the seventh planet to "Urectum" because its old name sounded impolite.
It's just that nobody in the White House understands how the phones work. Once they figure that out, they'll be in touch.
Now... It's pick up the receiver, then select a line... No wait, select a line, then press the speaker button, then dial '9' for an outside line? Or is it '6' for international calls, then '011'? No, use '9', but drop the '0' and dial --
Hello? Is someone there?
Biting the hand that feeds IT © 1998–2020