Well, yeah, that's other drawback... a ceramic rotor won't take much abuse before shattering. (that said, my brake pads are ceramic.) And they aren't balanced for 10k RPM. The steel ones can cope with it better, but I wouldn't trust them at that speed for long -- enough for a run, sure -- and never more than once. (after a full braking, I would never trust them again.)
In order for friction to destroy steel, it needs to actually wear it away one particle at a time.
Not entirely correct. While that may be the most common aging / failure method on a road car. On a race car, heat effects are what kills rotors -- of all construction. When you heat a steal (cast iron) rotor near (or past) the glass transition point (the point where it "melts", or transitions from solid to liquid) it will wear quickly and unevenly, begin to warp, and start developing cracks. Look at any used rotors from a race car; almost all of them have small, spider cracks in the braking surface from the repeated heat cycles. (heat causes metal to expand, but the heat isn't applied evenly over the entire disc, and it's a circle so the inside will expand more than the outside.)
But yes, in this equation, mass wins. Carbon fibre is great for many repeated, brief, super high heat cycles -- which is why F1 uses them. In this case, it's one HUGE prolonged dump of energy. That sort of thing will shatter a carbon rotor.
Re:Hash algorithm? Static salt like eBay Japan?
on
eBay Compromised
·
· Score: 1
And none of that is remotely a secret. Wow, they stole a page out of a phone book! (mostly, email and DoB are a google away.)
There has been volumes of research proving the exact opposite. Increased complexity and forced password changes invariably lead to much weaker passwords. People find a password they can remember that passes the (often idiotic) complexity rules, and add a rotating tag (0, A, symbol, etc.) to the beginning or end every time they're forced to change it. Or WORSE, they write it down and stick it on the monitor, wall next to the monitor, side of the computer, etc.
Actually, once a code is used, it cannot be reused. So even if you watched me login, and typed in the exact same thing within seconds, SecureID would deny the second login, and most likely flag the account -- your next login would be answered with a "next code" challenge. (I've worked at a place that would disable your account if that happens.)
Already happening. (note: most things that have the bandwidth to actually be useful for such things a) don't run SNMP (colo hosts), or b) are run by people with a clue who limit access to SNMP.)
Actually, for phones that have GPS, when dialing a recognized emergency number (911 in the US), the phone automatically enables the GPS and sends it's location. You don't even have to speak for police/fire/rescue to find you.
Correction... they know the address of where the line is supposed to terminate. If you tap the line, which is trivial -- and also a felony in the US, it's very hard to know where the caller actually is. And if there are bridge taps on the line -- which is still a large number today, it's that much harder to trace, as the line literally branches all over the place.
It's *possible*, but the attacker would have to be close enough for almost any weapon to be useless from the start. I.e. if you want until the attacker is touching you to draw, it's not going to go well. If she draws at 6 feet, the gun will be empty by the time the attacker gets to her. (and hopefully, some of those bullets will have hit said attacker -- in a panic, your aim will be "off".)
Indeed. They were sniffing around the College of Textiles (!) in '95 when I was graduating. We were one of the few departments that required FORTRAN (77).
(I had been campaigning since '93 to stop that shit. 'tho it paid well as a Lab Instructor (aka "TA".) They switched to Java (ugg) in '96-97.)
Not so much that it "doesn't fit", but that some things are a pain to do and the compilers suck at handling it. (eg. array math. even 2 dimensions is a mess in C/C++)
They both generate machine code. But they get there in different ways and produce very different output. It would be more correct to say FORTRAN (compilers) blows away any C compilers. (esp. gcc)
IPv4 DHCP can take from 3 to 15s to setup. And waiting for IPv6 initialization on a network with no IPv6 adds to that. I suppose you've never paid any attention to how long network startup takes from any distro installer -- or during normal boot. If it's not a static configuration, it'll take a real, measurable, annoying amount of time to bring up.
Do you have an android device that turns off the wifi when not "on"? It takes a annoying amount of time for that to setup before any network apps can work. (and then 27 background apps attempt to sync at the same time.)
This is bullshit. You don't (read: should not have to) add every printer you happen to be standing next to -- which could accumulate to hundreds of printers. There are NUMEROUS technologies to allow printing to locally available printers, through a single system-wide printer. On my previous laptop (granted, that's windows...) I had a single "internet printer" loaded for printing to hotel printers. One system printer, one driver, and I can print to any customer facing printer in any Hilton on the planet. Today, it's called "Cloud Printing".
Neither does GRUB 1. And in fact, both are usable with any config file. It's just that every distro out there has means for automatic generation of grub.cfg (menu.lst) to support random kernel packages.
Sure, point out a thing that's been auto-loading (kernel modules) much longer than systemD has been dreamed of. Network configuration -- even wireless -- has been user configurable by various packages for ages. (Linus' rant aside.) You'd want the network running LONG before any app is started that needs it, or do you enjoy having a 15s delay before chrome can be used; every time you start chrome? (btw, practically everything uses the network these days.)
Linus was referring to the insanity of "security" today. Anything that can add a driver (eg. in windows or macos, adding a printer will add a driver) is an "unsafe" operation -- and rightly so, as too many bits of crap piggyback their way into systems this way. And no, Linus, adding a printer is not "an everyday task." The last time I added a printer was after re-imaging a workstation for a new hire at work. That was 2 months ago.
No, the reason "everyone" choses systemD is because they don't know any better. (aka. "peer pressure") systemD is a very dangerous weed, designed and maintained by someone with a history of half-assing his projects and ignoring everyone else. It replaces and re-implements a number of well established, stable, very well understood, highly bug free (due to simplicity, and shear age of the code) software packages... that an INIT SYSTEM has no reason to be. I understand the appeal for distro maintainers... demand starting for desktop environments, built-in dependency system, etc. But for the most part, SysVinit handled everything already. (not demand start, but that's very UNIX anyway: in UNIX(tm), things start when they're configured to during boot, or when a USER f***ing starts them.)
To be fair, LILO is very primitive and sensitive. It doesn't read filesystems; it has an installed map (the result of running lilo) that lists the exact blocks to load for a given entry. You cannot load anything that's not in its map. Touch any of those blocks and it can fall apart. GRUB was a vast improvement, but also adds a great deal of complexity. (GRUB2 even more so.)
The end-of-year forms don't show up in the online banking systems. And while you can see and pay taxes online, they require an "online payment code" which is a random 5 digit number on the bill -- it used to be the last 5 digits of the title, but for the last several years, it's been a random number. (and they wonder why so many people never pay their property taxes. They've rolled vehicle tax into your plate renewal, which means no one has any idea how much *cash* they have to take to the DMV, now.)
They had issues long before Congress' lame mandate. I stand by what I said... there are far too many people involved in almost every part of the USPS system[*]. Most (all?) of them are paid well more than they should for what they do. And about the only way to get fired is get sent to jail.
[*] except where people are actually needed -- at the counter. I've been in lots of post offices across the country, and you've got to get way out in the sticks to find a post office where there isn't a line of 37 people waiting on the one rude asshole working the counter.
Actually, it was entirely possible to opt-out of bulk mail in years (decades?) past. But as "bulk mail" is almost their entire source of income, that's not remotely an option today. Sadly, all this does is create literally tones of trash every week. (go by any apartment complex mail room on Wed and there will be mountains of junk mail in the trash. At my former complex, there'd be half a dumpster worth of junk mail discarded every week.)
Junk mail may be 99% of their income, but it's far from profitable, and 1st class is nowhere near cheap. The USPS involves far too many people, who are paid far too much, and is worse than every union combined to try to get rid of anyone.
"Bulk mail" is pretty much their only customer these days. The general population receives a fair amount, but sends almost none. And the majority of what we receive doesn't need to be paper... I have about 5 things every year that isn't available to me any other way -- and they're all tax BS (1099, 1098, and property tax bills)
Slashdot Mirror
Too lazy (or stupid) to use a search engine?
Here's one to get you started... http://cs.unc.edu/~fabian/pape... Feel free to continue down the rabbit hole from their references.
Well, yeah, that's other drawback... a ceramic rotor won't take much abuse before shattering. (that said, my brake pads are ceramic.) And they aren't balanced for 10k RPM. The steel ones can cope with it better, but I wouldn't trust them at that speed for long -- enough for a run, sure -- and never more than once. (after a full braking, I would never trust them again.)
Not entirely correct. While that may be the most common aging / failure method on a road car. On a race car, heat effects are what kills rotors -- of all construction. When you heat a steal (cast iron) rotor near (or past) the glass transition point (the point where it "melts", or transitions from solid to liquid) it will wear quickly and unevenly, begin to warp, and start developing cracks. Look at any used rotors from a race car; almost all of them have small, spider cracks in the braking surface from the repeated heat cycles. (heat causes metal to expand, but the heat isn't applied evenly over the entire disc, and it's a circle so the inside will expand more than the outside.)
But yes, in this equation, mass wins. Carbon fibre is great for many repeated, brief, super high heat cycles -- which is why F1 uses them. In this case, it's one HUGE prolonged dump of energy. That sort of thing will shatter a carbon rotor.
And none of that is remotely a secret. Wow, they stole a page out of a phone book! (mostly, email and DoB are a google away.)
There has been volumes of research proving the exact opposite. Increased complexity and forced password changes invariably lead to much weaker passwords. People find a password they can remember that passes the (often idiotic) complexity rules, and add a rotating tag (0, A, symbol, etc.) to the beginning or end every time they're forced to change it. Or WORSE, they write it down and stick it on the monitor, wall next to the monitor, side of the computer, etc.
Actually, once a code is used, it cannot be reused. So even if you watched me login, and typed in the exact same thing within seconds, SecureID would deny the second login, and most likely flag the account -- your next login would be answered with a "next code" challenge. (I've worked at a place that would disable your account if that happens.)
Already happening. (note: most things that have the bandwidth to actually be useful for such things a) don't run SNMP (colo hosts), or b) are run by people with a clue who limit access to SNMP.)
Actually, for phones that have GPS, when dialing a recognized emergency number (911 in the US), the phone automatically enables the GPS and sends it's location. You don't even have to speak for police/fire/rescue to find you.
Correction... they know the address of where the line is supposed to terminate. If you tap the line, which is trivial -- and also a felony in the US, it's very hard to know where the caller actually is. And if there are bridge taps on the line -- which is still a large number today, it's that much harder to trace, as the line literally branches all over the place.
...or a buttset (aka. lineman's handset) at a crossbox. There's still a lot of POTS in the world, and those boxes are the least "secure" shit around.
VoIP "toll fraud" (hacking, spoofing, out-right theft, etc.) is by far the world leader today.
*cough*VoIP*cough* (toll fraud is everywhere)
It's *possible*, but the attacker would have to be close enough for almost any weapon to be useless from the start. I.e. if you want until the attacker is touching you to draw, it's not going to go well. If she draws at 6 feet, the gun will be empty by the time the attacker gets to her. (and hopefully, some of those bullets will have hit said attacker -- in a panic, your aim will be "off".)
Indeed. They were sniffing around the College of Textiles (!) in '95 when I was graduating. We were one of the few departments that required FORTRAN (77).
(I had been campaigning since '93 to stop that shit. 'tho it paid well as a Lab Instructor (aka "TA".) They switched to Java (ugg) in '96-97.)
Not so much that it "doesn't fit", but that some things are a pain to do and the compilers suck at handling it. (eg. array math. even 2 dimensions is a mess in C/C++)
They both generate machine code. But they get there in different ways and produce very different output. It would be more correct to say FORTRAN (compilers) blows away any C compilers. (esp. gcc)
IPv4 DHCP can take from 3 to 15s to setup. And waiting for IPv6 initialization on a network with no IPv6 adds to that. I suppose you've never paid any attention to how long network startup takes from any distro installer -- or during normal boot. If it's not a static configuration, it'll take a real, measurable, annoying amount of time to bring up.
Do you have an android device that turns off the wifi when not "on"? It takes a annoying amount of time for that to setup before any network apps can work. (and then 27 background apps attempt to sync at the same time.)
This is bullshit. You don't (read: should not have to) add every printer you happen to be standing next to -- which could accumulate to hundreds of printers. There are NUMEROUS technologies to allow printing to locally available printers, through a single system-wide printer. On my previous laptop (granted, that's windows...) I had a single "internet printer" loaded for printing to hotel printers. One system printer, one driver, and I can print to any customer facing printer in any Hilton on the planet. Today, it's called "Cloud Printing".
Neither does GRUB 1. And in fact, both are usable with any config file. It's just that every distro out there has means for automatic generation of grub.cfg (menu.lst) to support random kernel packages.
Sure, point out a thing that's been auto-loading (kernel modules) much longer than systemD has been dreamed of. Network configuration -- even wireless -- has been user configurable by various packages for ages. (Linus' rant aside.) You'd want the network running LONG before any app is started that needs it, or do you enjoy having a 15s delay before chrome can be used; every time you start chrome? (btw, practically everything uses the network these days.)
Linus was referring to the insanity of "security" today. Anything that can add a driver (eg. in windows or macos, adding a printer will add a driver) is an "unsafe" operation -- and rightly so, as too many bits of crap piggyback their way into systems this way. And no, Linus, adding a printer is not "an everyday task." The last time I added a printer was after re-imaging a workstation for a new hire at work. That was 2 months ago.
No, the reason "everyone" choses systemD is because they don't know any better. (aka. "peer pressure") systemD is a very dangerous weed, designed and maintained by someone with a history of half-assing his projects and ignoring everyone else. It replaces and re-implements a number of well established, stable, very well understood, highly bug free (due to simplicity, and shear age of the code) software packages... that an INIT SYSTEM has no reason to be. I understand the appeal for distro maintainers... demand starting for desktop environments, built-in dependency system, etc. But for the most part, SysVinit handled everything already. (not demand start, but that's very UNIX anyway: in UNIX(tm), things start when they're configured to during boot, or when a USER f***ing starts them.)
To be fair, LILO is very primitive and sensitive. It doesn't read filesystems; it has an installed map (the result of running lilo) that lists the exact blocks to load for a given entry. You cannot load anything that's not in its map. Touch any of those blocks and it can fall apart. GRUB was a vast improvement, but also adds a great deal of complexity. (GRUB2 even more so.)
Wake Co., NC / NC SECU
The end-of-year forms don't show up in the online banking systems. And while you can see and pay taxes online, they require an "online payment code" which is a random 5 digit number on the bill -- it used to be the last 5 digits of the title, but for the last several years, it's been a random number. (and they wonder why so many people never pay their property taxes. They've rolled vehicle tax into your plate renewal, which means no one has any idea how much *cash* they have to take to the DMV, now.)
They had issues long before Congress' lame mandate. I stand by what I said... there are far too many people involved in almost every part of the USPS system[*]. Most (all?) of them are paid well more than they should for what they do. And about the only way to get fired is get sent to jail.
[*] except where people are actually needed -- at the counter. I've been in lots of post offices across the country, and you've got to get way out in the sticks to find a post office where there isn't a line of 37 people waiting on the one rude asshole working the counter.
Actually, it was entirely possible to opt-out of bulk mail in years (decades?) past. But as "bulk mail" is almost their entire source of income, that's not remotely an option today. Sadly, all this does is create literally tones of trash every week. (go by any apartment complex mail room on Wed and there will be mountains of junk mail in the trash. At my former complex, there'd be half a dumpster worth of junk mail discarded every week.)
Junk mail may be 99% of their income, but it's far from profitable, and 1st class is nowhere near cheap. The USPS involves far too many people, who are paid far too much, and is worse than every union combined to try to get rid of anyone.
"Bulk mail" is pretty much their only customer these days. The general population receives a fair amount, but sends almost none. And the majority of what we receive doesn't need to be paper... I have about 5 things every year that isn't available to me any other way -- and they're all tax BS (1099, 1098, and property tax bills)