Not guaranteed, just orders of magnitude more reliable in places with shoddy mobile phone reception.
I'm in Japan and carried a pager until about 10 years ago when the major carrier shut down their service. Within the first month our on-call people missed multiple pages due to signal-related issues.
For certain types of authentication you do need to store plaintext passwords - the traditional two types of logins used for dialups/pppoe are PAP and CHAP. PAP allows you to have password hashes on the auth server but transmits plaintext on the wire/air. Conversely CHAP hashes on the wire/air but requires the plaintext password to be available on the auth server due to the nature of the protocol. You choose your points of vulnerability.
The one consistent about Heinlein books was Heinlein blatantly shoveling his political views at the time (which changed over the years) down your throat.
Your arguments against Unicode are pretty weaksauce. If you want strong basis to criticize it, I suggest reading about Han unification and the clusterfuck it really is.
Over 136,000 characters in Unicode and people still can't make their name display right without quirky variant selectors.
Found a gaping goatse-sized security vulnerability in a package that had been outsourced and the original contractors long since gone.
It was less expensive to just kill the product which we had been selling for about 3 years than to re-engineer the thing from the ground up with new staff.
There are dozens of alternative chips that can be used:
Prolific (have had their own driver sabotage issues in the past and even the genuine ones are kind of crappy) Silicon Labs WinChipHead (I have these on my Arduino-compatibles, seem to work OK) More chips than I can rattle off from Microchip and Atmel And a bunch of others.
Around 1990 I came up with a guideline that a power user should always spend USD500 on memory for their desktop. That target roughly held true for over 15 years until the price of memory plummeted in the mid-2000s and you couldn't fit that much in.
This takes away the fun I used to have with old failing hard drives: Install a webserver in a test rig with webcam pointed at the disk sitting out on a workbench, then remove the top cover and see how long it would live.
During an earlier DNS amplification attack we actually identified over 1000 of our customers that had their CPE devices misconfigured to expose the onboard resolver to the internet at large.
After contacting them we had a less than 1% rectification rate.
As often as not it is a judgement call of cost to fix vs. risk.
We have the situation where we have a pair of open resolvers whose addresses have been constant for the past 17 years. We have about a quarter million customers, some who have those addresses embedded into devices whose passwords have been long since forgotten.
The amount of support time needed to deal with these customers from putting in ACLs to the resolvers would run into the many many thousands of staff-hours.
As we were affected by a somewhat similar attack (a DNS amplification DDoS but with different mechanics, bouncing queries off of CPE with open forwarding resolvers) last year we drop TYPE=ANY queries (I've yet to see a legitimate production query of that type ever) and rate-limit queries but access lists on the servers would require such a huge expense that its not likely to happen any time soon.
Slashdot Mirror
Not guaranteed, just orders of magnitude more reliable in places with shoddy mobile phone reception.
I'm in Japan and carried a pager until about 10 years ago when the major carrier shut down their service. Within the first month our on-call people missed multiple pages due to signal-related issues.
As a japanese resident of over 20 years I still wouldn't give up my current citizenship to naturalize even though it'd be easy.
For certain types of authentication you do need to store plaintext passwords - the traditional two types of logins used for dialups/pppoe are PAP and CHAP. PAP allows you to have password hashes on the auth server but transmits plaintext on the wire/air. Conversely CHAP hashes on the wire/air but requires the plaintext password to be available on the auth server due to the nature of the protocol. You choose your points of vulnerability.
The one consistent about Heinlein books was Heinlein blatantly shoveling his political views at the time (which changed over the years) down your throat.
What subnetting? Nearly everything in v6 is a /64.
Trying to scan a v6 /64 subnet (what a consumer gets 98% of the time) is like trying to find a single machine in the entire public v4 internet.
Your arguments against Unicode are pretty weaksauce. If you want strong basis to criticize it, I suggest reading about Han unification and the clusterfuck it really is.
Over 136,000 characters in Unicode and people still can't make their name display right without quirky variant selectors.
They were still in use at Bell Labs in 1997 when I left. On Vaxen.
Found a gaping goatse-sized security vulnerability in a package that had been outsourced and the original contractors long since gone.
It was less expensive to just kill the product which we had been selling for about 3 years than to re-engineer the thing from the ground up with new staff.
There are dozens of alternative chips that can be used:
Prolific (have had their own driver sabotage issues in the past and even the genuine ones are kind of crappy)
Silicon Labs
WinChipHead (I have these on my Arduino-compatibles, seem to work OK)
More chips than I can rattle off from Microchip and Atmel
And a bunch of others.
Around 1990 I came up with a guideline that a power user should always spend USD500 on memory for their desktop. That target roughly held true for over 15 years until the price of memory plummeted in the mid-2000s and you couldn't fit that much in.
SSL certs are pretty trivial to track in Nagios or whatever your monitoring software of choice is.
No two domain registrars seem to format their WHOIS data the same though, making it a lot harder.
There is no hyphen in expat. Sorry, pet peeve.
Explosive bolts for jettisoning failing drives.
Stand clear!
This takes away the fun I used to have with old failing hard drives: Install a webserver in a test rig with webcam pointed at the disk sitting out on a workbench, then remove the top cover and see how long it would live.
Just send the space shuttle up to fix it.
Oh wait...
I've seen specialized stuff in production on 2.6 as recently as a couple years ago.
FLET's is not filtered at NTT's level. It all gets passed off to the individual ISPs who have to handle transit and filtering themselves.
au Hikari is a different situation.
Disclaimer: I work for a japanese ISP.
During an earlier DNS amplification attack we actually identified over 1000 of our customers that had their CPE devices misconfigured to expose the onboard resolver to the internet at large.
After contacting them we had a less than 1% rectification rate.
There are some patches for bind that surfaced about 6 months ago during some previous large-scale DNS amplification attacks.
I'd check nanog or bind-users mailing list archives around that time.
And of course with this "feature" it will never support DNSSEC ever.
As often as not it is a judgement call of cost to fix vs. risk.
We have the situation where we have a pair of open resolvers whose addresses have been constant for the past 17 years. We have about a quarter million customers, some who have those addresses embedded into devices whose passwords have been long since forgotten.
The amount of support time needed to deal with these customers from putting in ACLs to the resolvers would run into the many many thousands of staff-hours.
As we were affected by a somewhat similar attack (a DNS amplification DDoS but with different mechanics, bouncing queries off of CPE with open forwarding resolvers) last year we drop TYPE=ANY queries (I've yet to see a legitimate production query of that type ever) and rate-limit queries but access lists on the servers would require such a huge expense that its not likely to happen any time soon.
USD 5 in 1979 works out to USD 16 today, give or take.
You can hack xbmc to make it use MX Player (which does do proper hardware accelleration on rk3066 sticks) do the heavy lifting.
Rockchip is one of the most (if not the most) source-release-hostile of all the chinese SoC makers.