"accidental consent" They make it as confusing and hard as humanly possible to find and select the "hell no" button. If you don't stop and read every single character on the screen, just hitting what immediately looks like "Next" WILL install their crap.
BRI: 2B+D (strip away the ISDN signaling and you get IDSL) PRI: 23B+D
A sole "24 channel PRI" is 100% USELESS as there's ZERO mechanism to signal calls. Yes, you can order 24B PRI's as part of a multi-PRI bundle. (see also: "nfast group") If you can afford the PRI, CPE, and ISP account that will allow you bond 23 channels, you can afford a traditional "dedicated" T1 circuit. (hint: that T1 will be cheaper)
For shear destruction, one cruise missile equipped with a nuke can do more damage than the entire battery of a battleship. And it's one, very small target that can be fired hundreds of miles away.
For intimidation, a modern nuclear powered super carrier is a very closer runner. Not that we park carriers close enough to be seen. Park a battleship a mile off shore... Note: the last battleship on active duty wasn't entirely a battleship anymore; it was refitted to launch cruse missiles -- the Missouri still had the deck guns, tho.
Name one (common) thing that can only be done via the native client? The flash client is a pain in the ass, but I've yet to run into a task it couldn't complete. (it might not be the fastest, or most straight forward method, 'tho)
As best I can tell, from their limited "weasel lawyer speak", they are complaining about the linux driver compatibility layer of VMware's kernel. Something that has been depreciated for some time now -- it never was all that great for performance, but did allow many hardware vendors to offer ESXi drivers with very little effort.
Even with JTAG (hint: most drives don't have a JTAG header), all you'd get is the tiny bootloader. Almost everyone stores the full firmware on the plater. (because a 32K flash is cheaper than 8M)
(NOTE: This is a **MAJOR** cause of drive failure. The protected sections where the firmware is stored is never "refreshed"; when it becomes too weak to read, the drive is a paperweight.)
The bees coat the plastic with their own wax, thus sealing the cells. When you harvest, the cells are split releasing the honey. Honey contact with plastic is minimal and only happens during harvest.
iOS has had per-app data counters for a very long time. (settings:cellular -- see the number under the app name? see the toggle to the right? see the "System Services" at the bottom?) Granted, *you* have to reset it every month.
Compared to??? The person who threw it away either didn't know Sears would replace it, or was simply too lazy to take it back. Doesn't matter how it broke, who owns it, or who returns it; when it's presented to them, it gets replaced. We're paying for quality that doesn't break in the first place, and when you do manage to break it (arc the tip off a screwdriver, snap off a ratchet using a 6ft pipe...) they replace it, no questions asked.
It's simply too easy these days to go on the internet and find a dozen sources that sell boxes of various cables for peanuts. The appeal of RS was being able to get odd electronic parts immediately. These days, they barely have anything -- and 95% of it is available everywhere.
I think that's all about costs. Notice how everything is being done at M5 (and the completely over-the-top gratuitous shots of the M5 sign) now. The show used to have it's own shop.
a) sizeof(some pointer) will not tell you the size of what it points to b) the error here is allocating space for 3 things and putting 4 in it. It doesn't matter what function you call if you tell it to copy sizeof(void *) too much.
The error is a simple mistake due to unnecessarily complex code.
... until their metasploit code is published and everyone can see how to use this error. All it takes is one example; ONE person figures out how to trigger shellcode, and it's game over. No matter how complex the situation, an exploit is an exploit. It doesn't matter if it takes 87 steps to set off a nuke, if you know those steps and complete them - *boom*.
Either you write very little code, very simple code, or no one is closely inspecting your code. People make mistakes - period.
This glibc error was a simple mistake... count 3 things, put 4 in there. But yes, if their code weren't in such a f'ing complicated mess (have these fools never head of stuct) this mistake would be harder to make.
Police who commit misconduct of any kind is are the extreme minority.
That we hear about in the national news... we aren't made aware of every bullet fired by officers (there's supposed to be paperwork when they discharge their weapon(s)) or their every infraction
That's a weak deterrent at best. First, criminals are rather stupid. Second, the smarter ones will find an easier target, the dumber ones get more firepower.
Actually, it's usually safer for all if the cops don't show up during the bank heist. That's how hostages get taken and people get shot/stabbed/etc. Plus, if they "get away", it's instantly the FBI's problem. (also, with technology what it is today, few ever totally get away with it.)
Not where they will be, but where their doughnut-eatin'-ass is currently parked. They're in cars that are most definitely mobile -- and likely running with the heat/ac on max. Just sitting there "cruiser spooning" isn't exactly doing their job.
Slashdot Mirror
"accidental consent" They make it as confusing and hard as humanly possible to find and select the "hell no" button. If you don't stop and read every single character on the screen, just hitting what immediately looks like "Next" WILL install their crap.
BRI: 2B+D (strip away the ISDN signaling and you get IDSL)
PRI: 23B+D
A sole "24 channel PRI" is 100% USELESS as there's ZERO mechanism to signal calls. Yes, you can order 24B PRI's as part of a multi-PRI bundle. (see also: "nfast group") If you can afford the PRI, CPE, and ISP account that will allow you bond 23 channels, you can afford a traditional "dedicated" T1 circuit. (hint: that T1 will be cheaper)
For shear destruction, one cruise missile equipped with a nuke can do more damage than the entire battery of a battleship. And it's one, very small target that can be fired hundreds of miles away.
For intimidation, a modern nuclear powered super carrier is a very closer runner. Not that we park carriers close enough to be seen. Park a battleship a mile off shore... Note: the last battleship on active duty wasn't entirely a battleship anymore; it was refitted to launch cruse missiles -- the Missouri still had the deck guns, tho.
Name one (common) thing that can only be done via the native client? The flash client is a pain in the ass, but I've yet to run into a task it couldn't complete. (it might not be the fastest, or most straight forward method, 'tho)
FLASH based, through a web page. And it's a horrible mash of crap compared to the native client.
When have their management tools (viclient) run on anything other than windows?
They dropped Server v1 because it's a thousand f'ing years old.
As best I can tell, from their limited "weasel lawyer speak", they are complaining about the linux driver compatibility layer of VMware's kernel. Something that has been depreciated for some time now -- it never was all that great for performance, but did allow many hardware vendors to offer ESXi drivers with very little effort.
Because that's worked so well for the seagate hybrid drives. (hint: no it doesn't)
Even with JTAG (hint: most drives don't have a JTAG header), all you'd get is the tiny bootloader. Almost everyone stores the full firmware on the plater. (because a 32K flash is cheaper than 8M)
(NOTE: This is a **MAJOR** cause of drive failure. The protected sections where the firmware is stored is never "refreshed"; when it becomes too weak to read, the drive is a paperweight.)
The bees coat the plastic with their own wax, thus sealing the cells. When you harvest, the cells are split releasing the honey. Honey contact with plastic is minimal and only happens during harvest.
iOS has had per-app data counters for a very long time. (settings:cellular -- see the number under the app name? see the toggle to the right? see the "System Services" at the bottom?) Granted, *you* have to reset it every month.
Compared to??? The person who threw it away either didn't know Sears would replace it, or was simply too lazy to take it back. Doesn't matter how it broke, who owns it, or who returns it; when it's presented to them, it gets replaced. We're paying for quality that doesn't break in the first place, and when you do manage to break it (arc the tip off a screwdriver, snap off a ratchet using a 6ft pipe...) they replace it, no questions asked.
I want my cables to work, thanks.
It's simply too easy these days to go on the internet and find a dozen sources that sell boxes of various cables for peanuts. The appeal of RS was being able to get odd electronic parts immediately. These days, they barely have anything -- and 95% of it is available everywhere.
I think that's all about costs. Notice how everything is being done at M5 (and the completely over-the-top gratuitous shots of the M5 sign) now. The show used to have it's own shop.
Really? A boiled peanut is a Boiled. Peanut. (still in the shell. vs. the common tin can of shelled, roasted crap from Planters.)
a) sizeof(some pointer) will not tell you the size of what it points to
b) the error here is allocating space for 3 things and putting 4 in it. It doesn't matter what function you call if you tell it to copy sizeof(void *) too much.
The error is a simple mistake due to unnecessarily complex code.
... until their metasploit code is published and everyone can see how to use this error. All it takes is one example; ONE person figures out how to trigger shellcode, and it's game over. No matter how complex the situation, an exploit is an exploit. It doesn't matter if it takes 87 steps to set off a nuke, if you know those steps and complete them - *boom*.
Either you write very little code, very simple code, or no one is closely inspecting your code. People make mistakes - period.
This glibc error was a simple mistake... count 3 things, put 4 in there. But yes, if their code weren't in such a f'ing complicated mess (have these fools never head of stuct) this mistake would be harder to make.
That we hear about in the national news... we aren't made aware of every bullet fired by officers (there's supposed to be paperwork when they discharge their weapon(s)) or their every infraction
That's a weak deterrent at best. First, criminals are rather stupid. Second, the smarter ones will find an easier target, the dumber ones get more firepower.
BONUS: then it becomes the FBI's problem, not yours.
Or, perhaps, and I'm just puttin' it out there... they use the app themselves. A good sniping position is only good until you're spotted.
Actually, it's usually safer for all if the cops don't show up during the bank heist. That's how hostages get taken and people get shot/stabbed/etc. Plus, if they "get away", it's instantly the FBI's problem. (also, with technology what it is today, few ever totally get away with it.)
And they aren't "patrolling" if they're just sitting there. In legal terms, that's "standing" for us Joe Citizens.
Not where they will be, but where their doughnut-eatin'-ass is currently parked. They're in cars that are most definitely mobile -- and likely running with the heat/ac on max. Just sitting there "cruiser spooning" isn't exactly doing their job.