Posts by asdfasdfasdfasdf 15 publicly visible posts • joined 26 Nov 2014
I think the answer is that it depends on how many adverts you watch. Ads are of the order of $0.30 for 1000. So if you watch 30,000 adverts they're onto a winner.
The real problem is that there isn't enough advertising $$$ to go around. Hence all the scam adverts on YouTube, etc...
Ignoring the fact that Novell owned the UNIX copyrights and that both SCO and Novell licensed all Linux code to everyone under GPL on their websites, SCO never presented any code in Linux that wasn't followed up and proven to be independently written.
My theory is that someone at SCO copied chunks of Linux code into SCO's code base, and they didn't realise it was that way around until *after* they started the lawsuit...
"My question is how do they know it's being exploited in the wild if it's a local exploit? "
What Google do is run honeypot clients that go around the Internet to see what happens. Presumably they hit a website that broke through a Chrome (or whatever) zero day, and then ran code that used this vulnerability escalating to Local Admin.
Any one security vulnerability is fairly limited, but most attackers are smart enough to chain several together.
"journal where the journal's employees have read a lot of papers"
That's how I *thought* these things worked. It actually turns out that not only do Journals not employ reviewers, they don't even pay them. To publish in a journal, you also have to peer review other papers for the journal.... ...and you don't get paid for it.
On mobile at least, the new site only shows 5 or so articles at a time. The old site could show 30 or so. Also on the old you could scroll left and right to make navigation much faster.
Basically it’s the mobile site curse - one very long vertical list.
Because DNS is publicly visible and has ttl caching, it is reasonably easy to spot someone hijacking. Also anyone can run DNSSEC, you don't need to trust the root authorities (although who you'd rather trust is an interesting question)...
In any case, at least there is only one DNSSEC chain, you won't get someone "accidentally" signing a certificate for www.Google.com or *. If all else fails, why not do what you do at the moment ***and*** use DNSSEC?
It's actually fairly easy to set up DNSSEC...
dnssec-keygen -K <keydir> -a RSASHA256 -b 2048 -f KSK mydomain.com
dnssec-keygen -K <keydir> -a RSASHA256 -b 2048 mydomain.com
dnssec-signzone -e +1y -K <keydir> -o mydomain.com zoneFile
And past the output of this in the parent zone (alongside your NS record).
dnssec-dsfromkey <KSK.key>
Quantum computer emulators exist, but you don't get the efficiency.
It's a bit like having to emulate multiplication by adding number a+a+a+a+....+a. You get the right answer, but it's **slow**
Quantum computers use superposition, which is a little like white-light being made up of different colours all doing their own thing, so the level of parallelism is going to be another slow thing to emulate.
If you think about it, classical computers are basically just NAND gates glued together, it's not surprising that they fundamentally can't do everything...
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
