DidgetMaster didn't say it restarted spontaneously.
When restarting on Windows 8 and 10, if there are pending updates that require a reboot, there is a "restart and apply updates" and another "restart witout updates." Unless the user is paying attention it is easy to click the restart and apply updates option.
Could the problem be that that the Unicode consortium's mission is complete? Much like any organization, once your goal is complete you don't depart and say "Okay, good job everyone!" Instead, you start making up worthless features until you destroy the simplicity and elegance of what you created. (cough...Firefox...ahem...Thunderbird...)
The headline says "Researchers Find Vulnerabilities In Microsoft's and Google's Short URL Services." Regardless of the ability to reverse-guess the shortened URLs, this is really the user's fault.
If a user creates a shortcut that contains their login credentials, then that is their choice. Embedding the credentials into the URL means they are not credentials any longer, they are just part of a long obfuscated URL. Further shortening it completely defeats the purpose.
A good developer takes pride in writing the simplest code possible to solve a problem. If another developer cannot understand it, is the problem the reviewer, or the coder?
Thank you. Where did you find this? I really did RTFAs and couldn't find it.
There should be many many keys that would match the hash. But I think the article said it found the "password" not the "key" so maybe that minimizes the possibilities. I suppose the code could try decrypting some bit of the MFT data to see what looks like a valid MFT, but it doesn't look like they did that.
Why would the authors of the ransomware store the key on the drive?
The source code is out there, but I don't know what the salsa hash is or any of that. I take it that the ransomware actually has the key stored on the hard drive?
This problem would exist even without the EULAs. The companies would just setup in some country where they can't easily be touched. Heck, they probably already are. Also: Did these extensions even have EULAs?
Impressive! I think you just applied exactly what the article is talking about! You: * Associated the author with religion. * Godwinned * Gave the author has a secret agenda * Never actually disagreed with anything the article said.
Female computer programmers make 72 cents for every dollar earned by male programmers. That difference is after researchers adjust for factors such as age, education, years of experience, job title, employer and location
But then the rest of the article disagrees completely:
For every dollar a man in this role earns, this is how much a woman makes:
Game Artist – $0.84
Information Security Specialist – $0.85
Data Specialist – $0.76
Software Architect – $0.89
SEO Strategist – $0.90
Front End Engineer – $0.90
Database Engineer – $0.90
Sharepoint Developer – $0.91
SAP Developer – $0.92
On the upside, two professions in great demand show women doing at or better than the national average: Software Engineer – $0.94 Mobile Developer – $0.97
I suspect the first sentence should say "That difference is before researchers adjust..." Going further, and reading the linked GlassDoor PDF, I can't even find a 72 cent number in there. So I'm totally confused as to how they got that introduction. Can anyone else make sense of this?
That doesn't matter. 1) The text wasn't in quotes, so the author of the summary is responsible for it. 2) Even if it was in quotes, the submitter and Slashdot editors are responsible for writing summaries that make sense. That may mean putting things in their own words, rather than copy/pasting text from the article.
Permit me to reword my statement then. "It is typical to address supreme court nominations quickly."
The average time between nomination and confirmation/rejection has been ~23 days, however over the last 50 years it's upwards of 60 days... the Bork nomination, the current record for a SCOTUS vacancy is 237 days
The senate held confirmation hearings on Bork within a few months, and rejected Bork's nomination about 100 some days after his nomination. I agree with you that it was pretty slow.
The unique thing here is that the Republicans are saying that they will not permit the confirmation hearing to start until a new president is sworn in, which is about 300 days. Taking your 60 day average, that would be almost a year before confirmation. And if he is rejected, then the clock keeps ticking. By comparison, the others confirmations were almost immediate.
DidgetMaster didn't say it restarted spontaneously.
When restarting on Windows 8 and 10, if there are pending updates that require a reboot, there is a "restart and apply updates" and another "restart witout updates." Unless the user is paying attention it is easy to click the restart and apply updates option.
Could the problem be that that the Unicode consortium's mission is complete? Much like any organization, once your goal is complete you don't depart and say "Okay, good job everyone!" Instead, you start making up worthless features until you destroy the simplicity and elegance of what you created. (cough...Firefox...ahem...Thunderbird...)
How do you know the hackers didn't come-up with the exploit themselves? Or that they didn't actually have it before the good guys did?
Good point.
Apparently not:
PS2 in 2000: $299
PS4 in 2015: $399
$399 in the year 2015 equals $285 in the year 2000
Exactly! I have created a 1-atom engine that produces 320 horsepower! It is a single atom, surrounded by a 3.0L N55 Turbocharged DOHC I-6.
The headline says "Researchers Find Vulnerabilities In Microsoft's and Google's Short URL Services." Regardless of the ability to reverse-guess the shortened URLs, this is really the user's fault.
If a user creates a shortcut that contains their login credentials, then that is their choice. Embedding the credentials into the URL means they are not credentials any longer, they are just part of a long obfuscated URL. Further shortening it completely defeats the purpose.
I'm not sure which way this goes.
A good developer takes pride in writing the simplest code possible to solve a problem. If another developer cannot understand it, is the problem the reviewer, or the coder?
Thank you. Where did you find this? I really did RTFAs and couldn't find it.
There should be many many keys that would match the hash. But I think the article said it found the "password" not the "key" so maybe that minimizes the possibilities. I suppose the code could try decrypting some bit of the MFT data to see what looks like a valid MFT, but it doesn't look like they did that.
Why would the authors of the ransomware store the key on the drive?
The source code is out there, but I don't know what the salsa hash is or any of that. I take it that the ransomware actually has the key stored on the hard drive?
thanks
aha!
Okay, so can you explain it to everyone else? Cuz I am still confused.
This problem would exist even without the EULAs. The companies would just setup in some country where they can't easily be touched. Heck, they probably already are. Also: Did these extensions even have EULAs?
Impressive! I think you just applied exactly what the article is talking about! You:
* Associated the author with religion.
* Godwinned
* Gave the author has a secret agenda
* Never actually disagreed with anything the article said.
Are you a professional agnotologist?
If there are more attacks launched via Tor than there is legitimate traffic, then perhaps we need more people to use Tor.
It's like how some states outlawed credit card surcharges, so businesses offered cash discounts instead. It's the same dang thing!
Something is fundamentally wrong with modern capitalism if selling to only one vendor, instead of all vendors, is more profitable.
Thanks. That's quite silly since those jobs are computer programmer jobs.
The first 2 sentences of the article are:
Female computer programmers make 72 cents for every dollar earned by male programmers. That difference is after researchers adjust for factors such as age, education, years of experience, job title, employer and location
But then the rest of the article disagrees completely:
For every dollar a man in this role earns, this is how much a woman makes:
Game Artist – $0.84
Information Security Specialist – $0.85
Data Specialist – $0.76
Software Architect – $0.89
SEO Strategist – $0.90
Front End Engineer – $0.90
Database Engineer – $0.90
Sharepoint Developer – $0.91
SAP Developer – $0.92
On the upside, two professions in great demand show women doing at or better than the national average:
Software Engineer – $0.94
Mobile Developer – $0.97
I suspect the first sentence should say "That difference is before researchers adjust..." Going further, and reading the linked GlassDoor PDF, I can't even find a 72 cent number in there. So I'm totally confused as to how they got that introduction. Can anyone else make sense of this?
The judge can't compel you to do something illegal. Neither can a police officer.
FYI: China is building solar power even if there is no one using the power, as a way to prop up the industry.
Yeah, they should have put the admin password in an XML file!
That doesn't matter.
1) The text wasn't in quotes, so the author of the summary is responsible for it.
2) Even if it was in quotes, the submitter and Slashdot editors are responsible for writing summaries that make sense. That may mean putting things in their own words, rather than copy/pasting text from the article.
Permit me to reword my statement then. "It is typical to address supreme court nominations quickly."
The average time between nomination and confirmation/rejection has been ~23 days, however over the last 50 years it's upwards of 60 days... the Bork nomination, the current record for a SCOTUS vacancy is 237 days
The senate held confirmation hearings on Bork within a few months, and rejected Bork's nomination about 100 some days after his nomination. I agree with you that it was pretty slow.
The unique thing here is that the Republicans are saying that they will not permit the confirmation hearing to start until a new president is sworn in, which is about 300 days. Taking your 60 day average, that would be almost a year before confirmation. And if he is rejected, then the clock keeps ticking. By comparison, the others confirmations were almost immediate.