Ads within the app, WHILE I'M USING IT, are one thing. Going for the lame money grab of spamming my lockscreen with worthless, bandwidth robbing shit. Well, they can rot in the hottest, smelliest part of hell.
Translation error. Look at the pictures. That car did not ROLL. It FLIPPED, end over end. (a cart-wheel) Not a single piece of glass is even cracked, and there isn't a spec of dirt on the sides or roof. 95% of the damage is to the front -- where it plowed into a ditch at speed, and the remaining 5% in the back -- where it landed after flipping.
The lack of an engine in that front, MAY have contributed to the survivability, but Telsa isn't the only car to not have an engine in the front. (Nor are they remotely the first to do so.) What saved those kids is the 57 airbags that cocooned them. (and that they didn't fill the car with rusty razor blades.)
No they f'ing don't. You should drive more than 5 miles from your home sometime. The US is thousands of square miles. I've been up and down the east coast and yet to see a single gas station with those shrouds to seal the filler neck. And I'm not 100% sure those oddball pumps in CA are actually doing anything with the fumes.
Google's own braindamage is the reason why so few devices are actively patched. 6.0+ uses a filesystem block based patching mechanism. If you so much as mount the system partition (rw), you NEVER, EVER, EVER, EVER! get a single byte of patches.
And I don't know that the hell they're blabbering about... 4.4.4 absolutely does NOT get patches. Demanding I install 5.0.1 is not a patch. (it will then demand I install 5.1 then 6.0.) And unlike the majority of vendor "hacked" androids, Google doesn't ask a damn thing before it downloads hundreds of megs of crap I don't want -- tell me there's an update/patch/whatever and WAIT FOR ME TO APPROVE THE DOWNLOAD.
Come on, who hasn't done that at least once in their long carrier? Hell, I've done it on purpose a time or two. (it's actually rather rare for it to actually finish, or it used to be... shortly after rm and libc are deleted, things start Going Wrong(tm).)
Actually, it took the genius and determination of one person, and dozens of lives in the capturing of an actual enigma machine -- to learn the mechanics of the algorithm. Once you have the algorithm, brute force is a simple matter of equipment. And then, it's a simple matter to break it all by moving a single wire -- which they knew.
In all likelihood, they (assuming they actually had any hand in it at all) wrote poorly because they don't have a single f'ing clue how any technology works. They don't understand the danger of backdoors in crypto -- if "they" can get in, anyone else can too.
Or his own wiener. (or anyone else's for that matter -- except in cases of emergency, or by a licensed medical practitioner as part of a necessary medical procedure... and even then you must wear gloves and repeat aloud, "OMG, this is icky.")
"fix on next service" is not a RECALL. A recall is an immediate bring-it-in. Yes, some are more immediate than others -- eg. your wheel may fall off, vs. the third row seat *might* collapse in a crash.
It's hard to achieve perfection in an automated anti-spam system. Or would you rather have the listed-forever, extortion-esq system from SORBS? (the internet never forgets, or forgives)
If the network is down, then, AND ONLY THEN, will it's DHCP server answer queries. As the network isn't operational, you aren't going anywhere. When the network comes up, you still won't go anywhere with the 100-net addresses. The device is always a "gateway to the internet". That doesn't mean it's a router; a bridge is a gateway as well. (just at a different layer)
1.0.6.16 apparently has a "fix" -- they removed the buttons. If all they did was remove the clickable buttons but left the actual "reset.htm" pages in there, then it isn't fixed. As there are legitimate reasons to use those buttons (and no physical reset button), removing them is a Bad Idea(tm).
DOCSIS 1.0 security specifications REQUIRE firmware downloads through the HFC interface ONLY. Users CANNOT update DOCSIS compliant modems. In fact, END USERS have no access to vendor images in the first place. (If you happen to have your own CMTS, and thus "cable network", then yes, you can load practically anything you want -- i.e. anything the existing firmware will accept.)
Yes, you can hack your modem... open it, attach a JTAG header, and screw with the system. That is not what we're talking about.
What ISP? I want a list. That's not how the modem works. Factory reseting does not delete the modem from the ISP records. The "defaulting" just removes the learned values in the modem that allows it to find the network quickly. Otherwise, it has to search, channel by channel, for the DOCSIS network -- which it will do if it cannot find the network where it last did.
Indeed. And every SB device that's ever been made (all the way back to the SB3100) has had the same "flaw". There is no authentication at all, and if there were, 100% of them would be left at the static, insecure defaults because it's a freakin' modem with nothing to configure. (Or worse, the ISP will set the credentials to some random crap with no mechanism for the user to know them. They already do that with the integrated-router versions.)
(Yes, they *could* use the HFC MAC or SN, but we all know they won't.)
... or, IDK, listen to the complaints from the hundreds/thousands of customers who have pointed out their ~600million lies.
I've known about this for years. You cannot trust their geo data. It will never return an "I. Don't. F'ing. Know." Every IP you ask about, it WILL give you a location.
This has fuck all to do with "gender". That dumbass LAW specifies DNA. It doesn't matter if you have a wiener; your chromosomes dictate what bathroom you use.
The bathroom issue is what everyone wants to bitch about, yet it's the least important bit of bullshit that was part of that dumbass bill.
Our race car was like that. I loved it like that -- turn the wheel, the car leans over, and then it turns. Yes, you have to plan accordingly. You cannot wait to the last second to turn the wheel. Yes, that can be a problem at night with no (read: very ineffective) lights.
Right. Because Google doesn't arbitrarily shutdown services. One might think gmail, and apps for biz would be safe, but I wouldn't take that bet. (remember, they killed postini.)
Except that it doesn't actually work. (hint: the counter isn't stored in user flash.) Also, everyone is assuming the "erase me" flag is set. The phone gives ZERO indication that's been set.
Cisco's (enterprise) VoIP gear is not designed for, nor intended to be operated over the greater internet. VPNs sometimes work, but Skinny really isn't suited for many hops. (it's a very expressive protocol. Not quite to the point of button-down, button-up events, but close.) Their TFTP transfers come from the call manager (unless you intentionally set it up otherwise, which is just making a ton of work for yourself.) They support a mechanism for securing their configuration and all content they access (the CTL -- certificate trust list.) Firmware has been signed since v5.
And Cisco aren't the only ones using TFTP for boot-time configuration of VoIP hardware. The only phone I've yet seen that tried HTTP (HTTPS actually) first was an Avaya model made for the military/government markets.
(BTW, if you watch any of the Google data center walk through videos, every phone you see is an Avaya IP phone. If paired with Avaya's call manager, they aren't running SIP -- they use H.323)
The issue is with the initial connection. Setup an https site using just the general purpose cpu and throw a few hundred (or thousand) new connections per second at it. This isn't a problem for Joe Blow's Worthless Internet Hole Blog because it only gets a few dozen new connections per minute (if that.) It's a Real Problem for sites of any real size -- i.e. sites people would give a shit about it being encrypted like banks, paypal, ebay, webmail (eg. gmail), etc. Places like Slashdot... it's just stupid; it's not like there are any secrets here.
Yes, SSL sessions can be resumed, if the server saved the secret, and the client comes back before the keys expire. Are you connecting to Slashdot every 15min?
Slashdot Mirror
BULL. SHIT.
Ads within the app, WHILE I'M USING IT, are one thing. Going for the lame money grab of spamming my lockscreen with worthless, bandwidth robbing shit. Well, they can rot in the hottest, smelliest part of hell.
Translation error. Look at the pictures. That car did not ROLL. It FLIPPED, end over end. (a cart-wheel) Not a single piece of glass is even cracked, and there isn't a spec of dirt on the sides or roof. 95% of the damage is to the front -- where it plowed into a ditch at speed, and the remaining 5% in the back -- where it landed after flipping.
The lack of an engine in that front, MAY have contributed to the survivability, but Telsa isn't the only car to not have an engine in the front. (Nor are they remotely the first to do so.) What saved those kids is the 57 airbags that cocooned them. (and that they didn't fill the car with rusty razor blades.)
No they f'ing don't. You should drive more than 5 miles from your home sometime. The US is thousands of square miles. I've been up and down the east coast and yet to see a single gas station with those shrouds to seal the filler neck. And I'm not 100% sure those oddball pumps in CA are actually doing anything with the fumes.
If you don't count the tones of radioactive waste they produce.
Google's own braindamage is the reason why so few devices are actively patched. 6.0+ uses a filesystem block based patching mechanism. If you so much as mount the system partition (rw), you NEVER, EVER, EVER, EVER! get a single byte of patches.
And I don't know that the hell they're blabbering about... 4.4.4 absolutely does NOT get patches. Demanding I install 5.0.1 is not a patch. (it will then demand I install 5.1 then 6.0.) And unlike the majority of vendor "hacked" androids, Google doesn't ask a damn thing before it downloads hundreds of megs of crap I don't want -- tell me there's an update/patch/whatever and WAIT FOR ME TO APPROVE THE DOWNLOAD .
Come on, who hasn't done that at least once in their long carrier? Hell, I've done it on purpose a time or two. (it's actually rather rare for it to actually finish, or it used to be... shortly after rm and libc are deleted, things start Going Wrong(tm).)
Who says they're playing by Apple's paper rules? Furthermore, who says they're actually testing every build on every target platform?
Actually, it took the genius and determination of one person, and dozens of lives in the capturing of an actual enigma machine -- to learn the mechanics of the algorithm. Once you have the algorithm, brute force is a simple matter of equipment. And then, it's a simple matter to break it all by moving a single wire -- which they knew.
In all likelihood, they (assuming they actually had any hand in it at all) wrote poorly because they don't have a single f'ing clue how any technology works. They don't understand the danger of backdoors in crypto -- if "they" can get in, anyone else can too.
Or his own wiener. (or anyone else's for that matter -- except in cases of emergency, or by a licensed medical practitioner as part of a necessary medical procedure... and even then you must wear gloves and repeat aloud, "OMG, this is icky.")
"fix on next service" is not a RECALL. A recall is an immediate bring-it-in. Yes, some are more immediate than others -- eg. your wheel may fall off, vs. the third row seat *might* collapse in a crash.
It's hard to achieve perfection in an automated anti-spam system. Or would you rather have the listed-forever, extortion-esq system from SORBS? (the internet never forgets, or forgives)
No. It. Is. Not.
If the network is down, then, AND ONLY THEN, will it's DHCP server answer queries. As the network isn't operational, you aren't going anywhere. When the network comes up, you still won't go anywhere with the 100-net addresses. The device is always a "gateway to the internet". That doesn't mean it's a router; a bridge is a gateway as well. (just at a different layer)
1.0.6.16 apparently has a "fix" -- they removed the buttons. If all they did was remove the clickable buttons but left the actual "reset.htm" pages in there, then it isn't fixed. As there are legitimate reasons to use those buttons (and no physical reset button), removing them is a Bad Idea(tm).
DOCSIS 1.0 security specifications REQUIRE firmware downloads through the HFC interface ONLY. Users CANNOT update DOCSIS compliant modems. In fact, END USERS have no access to vendor images in the first place. (If you happen to have your own CMTS, and thus "cable network", then yes, you can load practically anything you want -- i.e. anything the existing firmware will accept.)
Yes, you can hack your modem... open it, attach a JTAG header, and screw with the system. That is not what we're talking about.
Or their modem wasn't a PoS that had no guard time between the +'s to stop this very thing.
What ISP? I want a list. That's not how the modem works. Factory reseting does not delete the modem from the ISP records. The "defaulting" just removes the learned values in the modem that allows it to find the network quickly. Otherwise, it has to search, channel by channel, for the DOCSIS network -- which it will do if it cannot find the network where it last did.
Indeed. And every SB device that's ever been made (all the way back to the SB3100) has had the same "flaw". There is no authentication at all, and if there were, 100% of them would be left at the static, insecure defaults because it's a freakin' modem with nothing to configure. (Or worse, the ISP will set the credentials to some random crap with no mechanism for the user to know them. They already do that with the integrated-router versions.)
(Yes, they *could* use the HFC MAC or SN, but we all know they won't.)
... or, IDK, listen to the complaints from the hundreds/thousands of customers who have pointed out their ~600million lies.
I've known about this for years. You cannot trust their geo data. It will never return an "I. Don't. F'ing. Know." Every IP you ask about, it WILL give you a location.
This has fuck all to do with "gender". That dumbass LAW specifies DNA. It doesn't matter if you have a wiener; your chromosomes dictate what bathroom you use.
The bathroom issue is what everyone wants to bitch about, yet it's the least important bit of bullshit that was part of that dumbass bill.
Our race car was like that. I loved it like that -- turn the wheel, the car leans over, and then it turns. Yes, you have to plan accordingly. You cannot wait to the last second to turn the wheel. Yes, that can be a problem at night with no (read: very ineffective) lights.
Right. Because Google doesn't arbitrarily shutdown services. One might think gmail, and apps for biz would be safe, but I wouldn't take that bet. (remember, they killed postini.)
Except that it doesn't actually work. (hint: the counter isn't stored in user flash.) Also, everyone is assuming the "erase me" flag is set. The phone gives ZERO indication that's been set.
Cisco's (enterprise) VoIP gear is not designed for, nor intended to be operated over the greater internet. VPNs sometimes work, but Skinny really isn't suited for many hops. (it's a very expressive protocol. Not quite to the point of button-down, button-up events, but close.) Their TFTP transfers come from the call manager (unless you intentionally set it up otherwise, which is just making a ton of work for yourself.) They support a mechanism for securing their configuration and all content they access (the CTL -- certificate trust list.) Firmware has been signed since v5.
And Cisco aren't the only ones using TFTP for boot-time configuration of VoIP hardware. The only phone I've yet seen that tried HTTP (HTTPS actually) first was an Avaya model made for the military/government markets.
(BTW, if you watch any of the Google data center walk through videos, every phone you see is an Avaya IP phone. If paired with Avaya's call manager, they aren't running SIP -- they use H.323)
The issue is with the initial connection. Setup an https site using just the general purpose cpu and throw a few hundred (or thousand) new connections per second at it. This isn't a problem for Joe Blow's Worthless Internet Hole Blog because it only gets a few dozen new connections per minute (if that.) It's a Real Problem for sites of any real size -- i.e. sites people would give a shit about it being encrypted like banks, paypal, ebay, webmail (eg. gmail), etc. Places like Slashdot... it's just stupid; it's not like there are any secrets here.
Yes, SSL sessions can be resumed, if the server saved the secret, and the client comes back before the keys expire. Are you connecting to Slashdot every 15min?