Aside from open networks like you've mentioned. Also, WPA2 allows offline password recovery when authentication is enabled and that's a really bad thing since many people like to use very simple digit only passwords which can be trivially guessed using a modern GPU and hashcat or using a service like GPUHash.
WPA3 still uses AES but with some additional quirks which shouldn't take too much CPU power 'cause the WPA standard takes low power/low performance devices into consideration.
It will definitely require a new version of the wpa_supplicant daemon and probably drivers will have to be updated as well, but other than that, I see no issues.
Too bad, my submission has been rejected even though it had a lot more information which I'll post anyways:
New security features include:
WPA3 uses the Simultaneous Authentication of Equals (SAE) algorithm, which replaces Pre-shared Key (PSK) in WPA2-Personal, while WPA3-Enterprise uses a more complex set of features that replace IEEE 802.1X from WPA2-Enterprise. These are: authenticated encryption, key derivation and confirmation, key establishment and authentication, robust management frame protection.
WPA3 is resistant to dictionary attacks. The Wi-Fi Alliance says that WPA3's SAE is resistant to offline dictionary attacks where an attacker tries to guess a Wi-Fi network's password by trying various passwords in a quick succession.
Wi-Fi Easy Connect for WPA2 and WPA3: This feature is aimed at smart (Internet of Things) devices that don't have a screen where a user can configure its Wi-Fi network settings. For example, a user will be able to use his phone or tablet to configure the WiFi WPA3 options of another device that doesn't have a screen, such as tiny IoT equipment like smart locks, smart light bulbs, and others.
Wi-Fi Enhanced Open: a proprietary technology, which uses an algorithm known as Opportunistic Wireless Encryption (OWE) to encrypt each connection between a WiFi user and the router/access point with its own custom encryption key. This per-user encryption prevents local attackers from snooping on other users' traffic, even if the network doesn't require a password to join.
Should professional sports switch to robot referees?
Let's talk when we have something close to AGI, something which is capable of thinking.
Right now we have pretty stupid and quite rigid algorithms which require tons of coding, colossal amounts of data to be trained, don't take any human conventions into account (unless they are again hard-coded into), and then these algos cannot understand, generalize, think, doubt and make rational conclusions. While the AI hype is extremely strong (because it attracts a lot of capital and venture capitalists aren't smart enough to see the lies), we have no actual intelligence.
TLDR: Hell, no. Ask in a 100 years. Referees could absolutely use the help of video recordings though.
Or maybe just maybe it's because Intel has almost squandered its competitive edge?
10nm is nowhere to be seen in decent quantities even though it was promised back in... 2016. In a recent earnings call mass production was delayed until 2019.
Ice Lake is nowhere to be seen and Intel is still rehashing its three (!) years old SkyLake uArch. Meanwhile AMD Zen uArch has a very strong IPC performance and is only lacking in top frequencies, however AMD CPUs also have a very competitive TDP.
Add Meltdown, Spectre, Brian Krzanich selling all his shares (and leaving the bare minimum allowed by corporate laws) to the mix and the picture becomes quite grim. Perhaps shareholders were happy to use this excuse to let him go. In another (successful) corporation and under different circumstances this incident perhaps would have been brushed under the carpet.
Hyperthreading v. hypervisors is a really difficult and long topic to talk about. There's a lot of information and performance comparisons on the net and in the end it boils down to the type of work that you're doing.
That's interesting, I figured databases would be largely I/O bound, not processor bound.
Depends on your type of work. On our servers (~4K connections per second) we're 100% CPU bound. If you have enough RAM to keep your DB in RAM (we do), only writes might be IO bound.
Note that SMT doesn't necessarily have a posive effect on performance; it highly depends on the workload. In all likelyhood it will actually slow down
First of all, it surely looks like OpenBSD developers don't even have a working spellchecker and perhaps they are correct, saying that it doesn't necessarily have a "posive" effect.
However, in all seriousness, I've seen at least two dozens tests of HT and in the worst case scenario it slows down your performance by less than a few percents, however, when we're talking servers, which nowadays run highly parallelized workloads where a single process may span several cores (nginx, mariadb, redis, mongodb, etc. etc. etc.) the performance gain from using HT may reach up to 30%, i.e. you're getting a third of your cores for free, which allows you to greatly cut expenditures and save on cooling.
Yes, HT poses security challenges in a multiuser environment (say, for a hosting provider) where people might run any code they want, however a typical application server almost always runs a tightly controlled software stack, which means your server processes cannot run any foreign code, which means Meltdown/Spectre class attacks might be safely disregarded.
... only for PoW alt-coins which are barely used. Bitcoin and Ethereum are safe. This kind of attack will be impossible against these two currencies unless you have hundreds of millions of dollars to spare.
PoS coins are not affected but they are vulnerable to another type of attack (network cloning) - no one has carried such an attack yet though.
I'm using anti-tracking add-ons, I don't accept 3d parties cookies, I have browser cache in memory, and I don't allow Facebook to be embedded on websites other than FB itself.
I'm on facebook and I'm happy: I just assume everything on my profile is publicly accessible. If you think otherwise you're either a gullible person or a clinical idiot. I just cannot understand how rational people can trust their data to be stored "safely" and "privately" by literally thousands of strangers whose only purpose is to make money off you.
Almost everything in this world can be weaponised, so stop BS'ing us, Google. You create technologies which will be used by military in one way or another.
Luckily we're not yet even remotely close to "intelligence" (which scientists have yet to define), so I'm glad this announcement is a sort of relief for some extremely gulliable people who cannot sleep at night after reading news headlines about an impending doom 'caused by Teminator like machines.
People used to go to war when then were 8-9-10-11-12 years of age. In fact even younger children in the modern world participate in all sorts of conflicts around the world. The western world isn't slightly inconvenienced by that last time I checked.
The fact that we arbitrarily raise the entry age of adulthood doesn't mean nature follows. It also doesn't mean that younger children don't know the concept of death and they shouldn't be taught to value life above everything else in this world. So, maybe, just maybe, it's not Valve's task to set arbitrary age limits. Maybe just maybe parents and society, through proper education, should set the priorities and values of the growing population.
Also, this giant loophole just cannot be solved technically unless you force children to authenticate using their birth certificate. Then someone should check its validity and... sorry, this can hardly be solved technically unless you put a Valve employee next to every child trying to log in to their account. You must realize it's simply impossible.
When you upload something to the cloud without first encrypting it using the keys only you know, then it automatically becomes public and known by third parties the moment it leaves your PC. So, what's all the fuss about? What kind of privacy did people/authorities actually expect? Or maybe they believed that the engineers in the said companies never pry into their users lives? Oh, wait, they do...
In short, you must only upload and share only the things you can show to the entire world. End of story. Oh, it's almost the same for unencrypted email and certain instant messengers.
3200MHz DDR4 doesn't run at 3200MHz - its actual clock rate is 1600MHz. 3200 here denotes its data transfer rate in millions of transfers per seconds.
https://en.wikipedia.org/wiki/...
It's the same Skylake uArch which debuted three years ago and naturally this particular CPU is affected by both Meltdown and Spectre. It's still an accomplishment though since it's the first ever consumer CPU to run at a such an insane clockrate.
Oh, and it will be available in very limited quantities.
"It highlights the idea that the data we use to train image recognition algorithms is reflected in the way the said algorithms calculate the world and how it behaves."
FTFY.
Please stop using the world "intelligence" gratuitously.
That's the marketing speak for, "Let's divert our customers and shareholders attention from the fact that our 10nm rollout is now three years late and still incomplete and the fact that we haven't updated our uArch in years (the last one was Skylake in... 2015) and AMD is closely trailing us in the IPC metric (which is considered the cornerstone of CPU performance) and with the advent of 7nm process from the competing fabs is around the corner and AMD has all the chances to make us irrelevant".
Oh, Qualcomm is about to introduce SnapDragon 1000 which is going to directly compete with Intel's ultra low-power/low-voltage CPUs.
Intel has just found itself irrelevant because having been a monopoly for so long has eaten the company from the inside.
Oh, and it's the middle of 2018 and we have yet to see their CPUs which have Meltdown (and Spectre to some extend) fixed in hardware. A bloody 12 months later year after the issue was reported to them. Instead Intel is about to rollout an anniversary 8086 CPU, which is the same old Coffee Lake (8700K) with a 5GHz turbo boost. WTF, Intel?!
To counter pretty inane comments here on./ I have to say this: it's impossible to understand who is involved and what's going on in this situation. One thing is clear: it's ugly.
The Kremlin wants to get access to Telegram's chats stored in the cloud by getting the encryption keys, and Durov claims such keys are impossible to share.
The issue is that the other "private" messengers in Russia work just fine and no one cares (WhatsApp, FB messenger, Viber, Signal, etc.), so you're left wondering whether they are indeed "secure" and your chats in them are not being spied on. Meanwhile it's well known that FSB can access your Skype history if you reside in Russia.
There's a conspiracy theory that it's all a clever ruse to get more people on Telegram (after all, this whole situation has made Telegram a lot more popular in the world than it was before) while those in power can actually read your correspondence in it (aside from p2p encrypted chats which people don't really use).
Durov can say and claim whatever he wants but your chats' history and files you send in Telegram are stored in plain text on Durov's servers. That alone should alert people but most don't care as long as it's advertised as "private" and "secure". It's certainly not private and it's not exactly clear whether it's indeed secure.
If you really care about privacy, use Signal or Wire.
Your numbering/naming scheme makes no sense at all!
It's really hard to say which of these SoCs are new/old faster/older: 425, 625, 626, 630, 636, 650, 651, 652, 653, 660, 710, 800, 801, 808, 810, 820, 821, 835, 845, etc. etc. etc.
Slashdot Mirror
Aside from open networks like you've mentioned. Also, WPA2 allows offline password recovery when authentication is enabled and that's a really bad thing since many people like to use very simple digit only passwords which can be trivially guessed using a modern GPU and hashcat or using a service like GPUHash.
WPA3 still uses AES but with some additional quirks which shouldn't take too much CPU power 'cause the WPA standard takes low power/low performance devices into consideration.
It will definitely require a new version of the wpa_supplicant daemon and probably drivers will have to be updated as well, but other than that, I see no issues.
Too bad, my submission has been rejected even though it had a lot more information which I'll post anyways:
New security features include:
Source
Let's talk when we have something close to AGI, something which is capable of thinking.
Right now we have pretty stupid and quite rigid algorithms which require tons of coding, colossal amounts of data to be trained, don't take any human conventions into account (unless they are again hard-coded into), and then these algos cannot understand, generalize, think, doubt and make rational conclusions. While the AI hype is extremely strong (because it attracts a lot of capital and venture capitalists aren't smart enough to see the lies), we have no actual intelligence.
TLDR: Hell, no. Ask in a 100 years. Referees could absolutely use the help of video recordings though.
Or maybe just maybe it's because Intel has almost squandered its competitive edge?
10nm is nowhere to be seen in decent quantities even though it was promised back in ... 2016. In a recent earnings call mass production was delayed until 2019.
Ice Lake is nowhere to be seen and Intel is still rehashing its three (!) years old SkyLake uArch. Meanwhile AMD Zen uArch has a very strong IPC performance and is only lacking in top frequencies, however AMD CPUs also have a very competitive TDP.
Add Meltdown, Spectre, Brian Krzanich selling all his shares (and leaving the bare minimum allowed by corporate laws) to the mix and the picture becomes quite grim. Perhaps shareholders were happy to use this excuse to let him go. In another (successful) corporation and under different circumstances this incident perhaps would have been brushed under the carpet.
Hyperthreading v. hypervisors is a really difficult and long topic to talk about. There's a lot of information and performance comparisons on the net and in the end it boils down to the type of work that you're doing.
https://medium.com/data-design...
https://medium.com/data-design...
https://medium.com/data-design...
https://www.phoronix.com/scan....
https://blogs.vmware.com/apps/...
https://blog.heroix.com/blog/s...
Also, last time I checked OpenBSD is not widely used as a virtualization platform.
Depends on your type of work. On our servers (~4K connections per second) we're 100% CPU bound. If you have enough RAM to keep your DB in RAM (we do), only writes might be IO bound.
First of all, it surely looks like OpenBSD developers don't even have a working spellchecker and perhaps they are correct, saying that it doesn't necessarily have a "posive" effect.
However, in all seriousness, I've seen at least two dozens tests of HT and in the worst case scenario it slows down your performance by less than a few percents, however, when we're talking servers, which nowadays run highly parallelized workloads where a single process may span several cores (nginx, mariadb, redis, mongodb, etc. etc. etc.) the performance gain from using HT may reach up to 30%, i.e. you're getting a third of your cores for free, which allows you to greatly cut expenditures and save on cooling.
Yes, HT poses security challenges in a multiuser environment (say, for a hosting provider) where people might run any code they want, however a typical application server almost always runs a tightly controlled software stack, which means your server processes cannot run any foreign code, which means Meltdown/Spectre class attacks might be safely disregarded.
How is the stock market different from the betting/gambling market.
... only for PoW alt-coins which are barely used. Bitcoin and Ethereum are safe. This kind of attack will be impossible against these two currencies unless you have hundreds of millions of dollars to spare.
PoS coins are not affected but they are vulnerable to another type of attack (network cloning) - no one has carried such an attack yet though.
I'm using anti-tracking add-ons, I don't accept 3d parties cookies, I have browser cache in memory, and I don't allow Facebook to be embedded on websites other than FB itself.
I'm on facebook and I'm happy: I just assume everything on my profile is publicly accessible. If you think otherwise you're either a gullible person or a clinical idiot. I just cannot understand how rational people can trust their data to be stored "safely" and "privately" by literally thousands of strangers whose only purpose is to make money off you.
Almost everything in this world can be weaponised, so stop BS'ing us, Google. You create technologies which will be used by military in one way or another.
Luckily we're not yet even remotely close to "intelligence" (which scientists have yet to define), so I'm glad this announcement is a sort of relief for some extremely gulliable people who cannot sleep at night after reading news headlines about an impending doom 'caused by Teminator like machines.
People used to go to war when then were 8-9-10-11-12 years of age. In fact even younger children in the modern world participate in all sorts of conflicts around the world. The western world isn't slightly inconvenienced by that last time I checked.
The fact that we arbitrarily raise the entry age of adulthood doesn't mean nature follows. It also doesn't mean that younger children don't know the concept of death and they shouldn't be taught to value life above everything else in this world. So, maybe, just maybe, it's not Valve's task to set arbitrary age limits. Maybe just maybe parents and society, through proper education, should set the priorities and values of the growing population.
Also, this giant loophole just cannot be solved technically unless you force children to authenticate using their birth certificate. Then someone should check its validity and ... sorry, this can hardly be solved technically unless you put a Valve employee next to every child trying to log in to their account. You must realize it's simply impossible.
When you upload something to the cloud without first encrypting it using the keys only you know, then it automatically becomes public and known by third parties the moment it leaves your PC. So, what's all the fuss about? What kind of privacy did people/authorities actually expect? Or maybe they believed that the engineers in the said companies never pry into their users lives? Oh, wait, they do ...
In short, you must only upload and share only the things you can show to the entire world. End of story. Oh, it's almost the same for unencrypted email and certain instant messengers.
3200MHz DDR4 doesn't run at 3200MHz - its actual clock rate is 1600MHz. 3200 here denotes its data transfer rate in millions of transfers per seconds. https://en.wikipedia.org/wiki/...
It's the same Skylake uArch which debuted three years ago and naturally this particular CPU is affected by both Meltdown and Spectre. It's still an accomplishment though since it's the first ever consumer CPU to run at a such an insane clockrate.
Oh, and it will be available in very limited quantities.
is a little bit too difficult to parse.
Here's a few human readable sources:
https://kernelnewbies.org/Linu...
https://www.phoronix.com/scan....
German: https://www.heise.de/ct/artike...
Russian: https://www.opennet.ru/opennew...
"It highlights the idea that the data we use to train image recognition algorithms is reflected in the way the said algorithms calculate the world and how it behaves."
FTFY.
Please stop using the world "intelligence" gratuitously.
Thank you,
people of the world.
That's the marketing speak for, "Let's divert our customers and shareholders attention from the fact that our 10nm rollout is now three years late and still incomplete and the fact that we haven't updated our uArch in years (the last one was Skylake in ... 2015) and AMD is closely trailing us in the IPC metric (which is considered the cornerstone of CPU performance) and with the advent of 7nm process from the competing fabs is around the corner and AMD has all the chances to make us irrelevant".
Oh, Qualcomm is about to introduce SnapDragon 1000 which is going to directly compete with Intel's ultra low-power/low-voltage CPUs.
Intel has just found itself irrelevant because having been a monopoly for so long has eaten the company from the inside.
Oh, and it's the middle of 2018 and we have yet to see their CPUs which have Meltdown (and Spectre to some extend) fixed in hardware. A bloody 12 months later year after the issue was reported to them. Instead Intel is about to rollout an anniversary 8086 CPU, which is the same old Coffee Lake (8700K) with a 5GHz turbo boost. WTF, Intel?!
To counter pretty inane comments here on ./ I have to say this: it's impossible to understand who is involved and what's going on in this situation. One thing is clear: it's ugly.
The Kremlin wants to get access to Telegram's chats stored in the cloud by getting the encryption keys, and Durov claims such keys are impossible to share.
The issue is that the other "private" messengers in Russia work just fine and no one cares (WhatsApp, FB messenger, Viber, Signal, etc.), so you're left wondering whether they are indeed "secure" and your chats in them are not being spied on. Meanwhile it's well known that FSB can access your Skype history if you reside in Russia.
There's a conspiracy theory that it's all a clever ruse to get more people on Telegram (after all, this whole situation has made Telegram a lot more popular in the world than it was before) while those in power can actually read your correspondence in it (aside from p2p encrypted chats which people don't really use).
Durov can say and claim whatever he wants but your chats' history and files you send in Telegram are stored in plain text on Durov's servers. That alone should alert people but most don't care as long as it's advertised as "private" and "secure". It's certainly not private and it's not exactly clear whether it's indeed secure.
If you really care about privacy, use Signal or Wire.
According to cocaine nose jobs from WallStreet?
(Sorry, I've never been convinced by the stock market - to me it's one enormous speculation).
I read, "How the Meth Men Overthrew the Mad Men". A confusion ensued.
Your numbering/naming scheme makes no sense at all!
It's really hard to say which of these SoCs are new/old faster/older: 425, 625, 626, 630, 636, 650, 651, 652, 653, 660, 710, 800, 801, 808, 810, 820, 821, 835, 845, etc. etc. etc.
It's sheer madness.