As was pointed out, this requires the encryption/decryption process to know how a credit card works and what makes one valid or invalid.
...and/or for the cleartext to include many more fake but valid-looking results than valid results, among which only the correct key picks the valid results and invalid keys pick incorrect results. That requires that invalid but plausible results are either easy to fabricate or can be fabricated offline rather than in realtime. Under certain circumstances, partial exposure of correct results, mixed in fake results, might even be desireable
You are obviously in a completely different situation than GP (with neighbors far away), if you can provision non-overlapping channels, because you could just put a trash SSID for all the 11b units out on one channel and use high speed on the rest.
But, if you are happy with 10M speeds to match your ISP uplink, you should be fine on an attenuated 11a or 11n/5G signal. Even in our buildings with internal brick walls you can still manage usable speeds on 5G through two walls.
Cisco is free if they want sell a 5GHz-only AP with a low power profile and a legacy 2.5GHz AP that daisies off of it. What they are complaining about in the article, though, is not being able to sell a 2.5GHz AP that does not support 11b and still call it "standards compliant." Since administrators are free to turn off 11b, this is just to save them a couple bucks per unit the next time they sell hundreds of thousands of units to a multinational.
FWIW 802.11ac requires line of sight and being relatively close to the AP to realize most of the benefits. But 11ac APs do seem to perform better as 11n APs than older 11n APs do. 802.11ad is intended for very short range use, and is more likely to be used e.g. for wireless docking stations than a serious mobile networking protocol.
"I think Stuxnet proved that: 1) there was a case for going after industrial control systems; 2) there was an impact in going after industrial control systems; and 3) showed that the devices and protocols were a valid target,” Toecker said. “And that caused interest in the security research community and they found this place is rife with vulnerabilities, low-hanging fruit."
...so they were apparently too busy not considering the very premise that people would hack them at all (up until stuxnet) to be arsed to consider vulnerable serial lines. RS232 is dead. Long live RS232.
It is self-defeating but not for the reasons you mention, as noted by other replies.
The reason it is self-defeating is that suppressing the salaries in fields where you badly need talent downregulates the cultivation of additional talent, and if the particular class of worker in question has any sideways mobility, may cause talent to leave those fields for either higher pay or easier work. A deficit in skills, whether highly compensated or not, negatively affects your end product, and even if you are colluding with competitors, negatively affects the market volume since there is less demand for crappy product. (For example, there is less demand now for Google hosted services than there would have been if they had not made a habit/reputation of pulling the rug out from underneath released products.)
It occurs to me that GP might have been focusing on application "versus" recruitment. Recruitment happens whether the applicant applies unsolicited or applies due to invite. Employers do not assume a self-initiated application is a done deal. The applicant could have many applications fielded. To *your* point, recruitment happens when determining benefits and wages in either case.
Once you add security and reliability to a wifi receiver, you are talking a good more silicon per unit. Which is why cheezy consumer-grade WiFi toys are so often completely insecure and unreliable. Those of us that don't mind running the cable would do so to escape having a cheezy, unreliable, insecure system controlling our environmental systems.
This is a knee-jerk over-reaction to poor educational experiences. Yes some educators throw useless memorization busy-work at students. No, memorization is not useless. Pulling things into fast-cache in wetware makes some forms of cognition possible that are not possible when pulling them off google or other reference material.
Believing "brightness" to be an intrinsic character trait is a psychological crutch for those who view their intelligence as their only redeeming quality. A large proportion of the variety of cognitive impairments can be overcome, many even cured, and people can and do get smarter. OP should be praised for embarking on a serious quest for self-improvement. If only those sitting on their laurels would do so as well.
Being one who has strong preferences about languages and routinely wears white socks with sandals, which has seldom ever been trendy, I have to say you are reading less into the gripes about programming languages than is there. Reality sets in the 200th or so time you type out InsanelyAribtraryFUNCTIONName(Nonsensically:formatted.thing_with_obscure_british_spelling_of_colour) and realize that there really is no solid underpinning to the particular language and people pretty much make up APIs and interfaces as they go along without even bothering to take the time to learn the pre-existing professional/academic vernacular around the subject matter at hand. After that, every time you type it you feel a bit of the life draining from you for participating in the perpetuation of such a flawed system. You start laughing a bit less at bike-shed-painting and take details more seriously. You start to bemoan the fact that injecting more arbitrary crap into the IT mindspace is not a long-term productivity winner for the field at large, and realizing that the guy who probably could code the machine to build the advanced surgical device you will quite likely need in 10 years, won't, because he spent most of his time sussing out such minutia as the differences between string.Template.substitute and string.Template.safe_substitute so that some advertising content could be appropriately targetted at 30-somethings that have a preference for clicking on pink buttons over blue.
Perl5 CGI::. text/html and response code of 200 is the default returned by header().
There are also tricks to get PHPish code-embedded-in-static-content look and feel from Perl, but mostly people don't use that due to a general recognition that only those crazy PHP coders want to deal with that level of clutter and it's better to keep the markup inside your quoting constructs.
Anyway, futher lambasting PHP would be BTDT at this point.
The first time I got an Android, I was utterly appalled that there was no note editing app in the base install.
I went looking for combined note/voice-note/picture/calander organizing apps. Most had too many strings attached (specific cloud-service sync options, or whatnot.) All of them lacked the ability to quickly procrastinate a task. You'd think that would be an obvious feature, but no. I went back to just remembering stuff with wetware. By the time my wetware starts to wear out, hopefully there will be something suitable.
Really the main problem I have with NetWorkManager on a surface UI level is that nobody seemed to deem it necessary to smooth out the case for people who just want to type their password in and NOT have it stored persistantly, just cached until reboot or (optionally) logout from the window manager. If you do not store your creds, it constantly asks you for them whenever it re-attaches to an SSID. Not only that but it stacks up multiple popup windows while you are AFK until your OS is lagging and your taskbar looks like a zip-tie. When you're validating an EAP cert there is NO REASON to do this EVER -- if you are presented with a validated cert from your home AAA server, re-using the creds shiuld be the default behavior.
The other major problem we have with Linux and Android's WiFi, both with and without NM, is that there are certain types of disassociation events after which the machine should run another DHCP transaction, and it doesn't. Wreaks havoc with dynamic authorization scenarios such as registration portals.
There is a use-case for utilities like NM -- wpa-supplicant and dhcpd and UI configuration utilities need to be glued together somehow, and if you have ipsec tunnels and l2tp running there is even more to be pasted together. NM does a poor job of it, but at least it does do the job.
Probably it was in the video, because people seem to think everyone has time to watch oodles of video without a posted transcript to skim over, and nobody cares to actually associate their hyperlinks to the text they attach the href to.
There's no quick tech fix for this. Mostly because the problem is partially cultural. Qualitative trust webs have to be academically validated, then essential behaviors to support them have to be installed in the population. It will take at least decades and most of the work will go completely unrewarded, because our monetary/compensation system is hopelessly corrupt, being that it also needs said fix.
As was pointed out, this requires the encryption/decryption process to know how a credit card works and what makes one valid or invalid.
...and/or for the cleartext to include many more fake but valid-looking results than valid results, among which only the correct key picks the valid results and invalid keys pick incorrect results. That requires that invalid but plausible results are either easy to fabricate or can be fabricated offline rather than in realtime. Under certain circumstances, partial exposure of correct results, mixed in fake results, might even be desireable
You are obviously in a completely different situation than GP (with neighbors far away), if you can provision non-overlapping channels, because you could just put a trash SSID for all the 11b units out on one channel and use high speed on the rest.
But, if you are happy with 10M speeds to match your ISP uplink, you should be fine on an attenuated 11a or 11n/5G signal. Even in our buildings with internal brick walls you can still manage usable speeds on 5G through two walls.
Cisco is free if they want sell a 5GHz-only AP with a low power profile and a legacy 2.5GHz AP that daisies off of it. What they are complaining about in the article, though, is not being able to sell a 2.5GHz AP that does not support 11b and still call it "standards compliant." Since administrators are free to turn off 11b, this is just to save them a couple bucks per unit the next time they sell hundreds of thousands of units to a multinational.
FWIW 802.11ac requires line of sight and being relatively close to the AP to realize most of the benefits. But 11ac APs do seem to perform better as 11n APs than older 11n APs do. 802.11ad is intended for very short range use, and is more likely to be used e.g. for wireless docking stations than a serious mobile networking protocol.
So I should rip up carpet and drill holes through walls to connect my television to my router?
Sure. Pre-run UTP would add value to any house I was considering buying.
Maye if you had bought an abgn radio for your hot new laptop and an abgn AP, neither your b devices nor your microwave oven would be slowing you down.
The real progress of 11ac is forcing consumers to buy 5gHz radios on their gadgets. 2.5GHz is for crap/old devices.
Oh for lack of a mod point.
According to the article:
"I think Stuxnet proved that: 1) there was a case for going after industrial control systems; 2) there was an impact in going after industrial control systems; and 3) showed that the devices and protocols were a valid target,” Toecker said. “And that caused interest in the security research community and they found this place is rife with vulnerabilities, low-hanging fruit."
...so they were apparently too busy not considering the very premise that people would hack them at all (up until stuxnet) to be arsed to consider vulnerable serial lines. RS232 is dead. Long live RS232.
It is self-defeating but not for the reasons you mention, as noted by other replies.
The reason it is self-defeating is that suppressing the salaries in fields where you badly need talent downregulates the cultivation of additional talent, and if the particular class of worker in question has any sideways mobility, may cause talent to leave those fields for either higher pay or easier work. A deficit in skills, whether highly compensated or not, negatively affects your end product, and even if you are colluding with competitors, negatively affects the market volume since there is less demand for crappy product. (For example, there is less demand now for Google hosted services than there would have been if they had not made a habit/reputation of pulling the rug out from underneath released products.)
It occurs to me that GP might have been focusing on application "versus" recruitment. Recruitment happens whether the applicant applies unsolicited or applies due to invite. Employers do not assume a self-initiated application is a done deal. The applicant could have many applications fielded. To *your* point, recruitment happens when determining benefits and wages in either case.
Except the fact that so many of the companies big enough to afford the better salaries and need lots of such engineers were in on it...
Once you add security and reliability to a wifi receiver, you are talking a good more silicon per unit. Which is why cheezy consumer-grade WiFi toys are so often completely insecure and unreliable. Those of us that don't mind running the cable would do so to escape having a cheezy, unreliable, insecure system controlling our environmental systems.
Just don't attach a IR receiver to them and you should be fine.
It goes like this:
PHB: So how's that App coming.
Coder: It is basically functional but we still need to work on the securi...
PHB: SHIP IT!
Education has nothing to do with memorization.
This is a knee-jerk over-reaction to poor educational experiences. Yes some educators throw useless memorization busy-work at students. No, memorization is not useless. Pulling things into fast-cache in wetware makes some forms of cognition possible that are not possible when pulling them off google or other reference material.
Believing "brightness" to be an intrinsic character trait is a psychological crutch for those who view their intelligence as their only redeeming quality. A large proportion of the variety of cognitive impairments can be overcome, many even cured, and people can and do get smarter. OP should be praised for embarking on a serious quest for self-improvement. If only those sitting on their laurels would do so as well.
My car does zero to 3.3 european swallow airspeed velococities (unladen) in 9.7 seconds. What does yours do?
Being one who has strong preferences about languages and routinely wears white socks with sandals, which has seldom ever been trendy, I have to say you are reading less into the gripes about programming languages than is there. Reality sets in the 200th or so time you type out InsanelyAribtraryFUNCTIONName(Nonsensically:formatted.thing_with_obscure_british_spelling_of_colour) and realize that there really is no solid underpinning to the particular language and people pretty much make up APIs and interfaces as they go along without even bothering to take the time to learn the pre-existing professional/academic vernacular around the subject matter at hand. After that, every time you type it you feel a bit of the life draining from you for participating in the perpetuation of such a flawed system. You start laughing a bit less at bike-shed-painting and take details more seriously. You start to bemoan the fact that injecting more arbitrary crap into the IT mindspace is not a long-term productivity winner for the field at large, and realizing that the guy who probably could code the machine to build the advanced surgical device you will quite likely need in 10 years, won't, because he spent most of his time sussing out such minutia as the differences between string.Template.substitute and string.Template.safe_substitute so that some advertising content could be appropriately targetted at 30-somethings that have a preference for clicking on pink buttons over blue.
The metric should be productivity with a modifier for the language's impact on the general mental and emotional well-being of the coder.
Perl5 CGI::. text/html and response code of 200 is the default returned by header().
There are also tricks to get PHPish code-embedded-in-static-content look and feel from Perl, but mostly people don't use that due to a general recognition that only those crazy PHP coders want to deal with that level of clutter and it's better to keep the markup inside your quoting constructs.
Anyway, futher lambasting PHP would be BTDT at this point.
The first time I got an Android, I was utterly appalled that there was no note editing app in the base install.
I went looking for combined note/voice-note/picture/calander organizing apps. Most had too many strings attached (specific cloud-service sync options, or whatnot.) All of them lacked the ability to quickly procrastinate a task. You'd think that would be an obvious feature, but no. I went back to just remembering stuff with wetware. By the time my wetware starts to wear out, hopefully there will be something suitable.
Have you seen the quality of the code written by the hardware design guys?
Yep. Atrocious. Topped only by BIOS coders. I have a laptop that you have to limit your BIOS sessions to under 1 minute or it will overheat. Animals.
Really the main problem I have with NetWorkManager on a surface UI level is that nobody seemed to deem it necessary to smooth out the case for people who just want to type their password in and NOT have it stored persistantly, just cached until reboot or (optionally) logout from the window manager. If you do not store your creds, it constantly asks you for them whenever it re-attaches to an SSID. Not only that but it stacks up multiple popup windows while you are AFK until your OS is lagging and your taskbar looks like a zip-tie. When you're validating an EAP cert there is NO REASON to do this EVER -- if you are presented with a validated cert from your home AAA server, re-using the creds shiuld be the default behavior.
The other major problem we have with Linux and Android's WiFi, both with and without NM, is that there are certain types of disassociation events after which the machine should run another DHCP transaction, and it doesn't. Wreaks havoc with dynamic authorization scenarios such as registration portals.
There is a use-case for utilities like NM -- wpa-supplicant and dhcpd and UI configuration utilities need to be glued together somehow, and if you have ipsec tunnels and l2tp running there is even more to be pasted together. NM does a poor job of it, but at least it does do the job.
Probably it was in the video, because people seem to think everyone has time to watch oodles of video without a posted transcript to skim over, and nobody cares to actually associate their hyperlinks to the text they attach the href to.
There's no quick tech fix for this. Mostly because the problem is partially cultural. Qualitative trust webs have to be academically validated, then essential behaviors to support them have to be installed in the population. It will take at least decades and most of the work will go completely unrewarded, because our monetary/compensation system is hopelessly corrupt, being that it also needs said fix.
If it is proprietary you have to make zero effort to conceal it.
Well, you should at least probably ensure you turned on the right compiler options to strip the NSA_BACKDOOR_PASSWORD identifier out of the binary.