You're confusing phone numbers with phone service. That's like confusing IP addresses with Internet service. Often they come together, and service providers can be dumb about letting consumers decouple them, but from a technical perspective there's no reason they need to have a 1:1 correlation.
If you've got a lock made in the last say, 50 years, and it's installed correctly, you can't open it with a credit card. Take a look at the latch of your exterior door and you'll see it's split into two independently moving parts. When the small part on the back of the latch is depressed -- as it should be when the door is closed -- the large portion of the latch cannot be moved except by turning the handle. This is intended specifically to defeat the slide-from-inside-to-out attack.
That doesn't stop someone from using any of the other viable attacks on standard doorknob locks, or just breaking a window or the like, but it does keep people from opening your door with a credit card.
Actually many hotspots *do* require you to use the local DNS server. It's pretty trivial, since that's part of the DHCP config, so it's not like end-users have to do anything to make that work. In those cases your data needs to be close enough to the DNS protocol to get propagated upstream, which is basically what iodine does.
Also note the SSH more or less requires TCP, so even if you allowed port 53 outbound you could limit access to the UDP protocol and effectively block SSH and many other tunneling tools, even if they are set to port 53. No DPI required. Sure, you'll prevent TCP DNS queries but that's rarely an issue of the kind of devices connecting to semi-open hotspots, particularly in the pre-payment phase of the connection.
Dropbox, or any other file sync utility, will happily transfer things between your phone and other computers anytime you're connected to the Internet. Which presumably on a smartphone is essentially constantly. Why you'd ever hassle with manual transfers confuses me.
You're assuming the purpose of the list is to catch terrorists. As you note it's probably worthless for that. But it's a great tool for harassing the citizenry, justifying government spending, etc.
That's not true at all. The X25 drives from Intel were terrible in terms of safe writes. The newer Intel drives are better, but only because they added a capacitor to allow in-process writes to complete -- simply being solid-state does not resolve these issues, and in some cases can make them much worse.
You don't need to support your statement. But you do need to explain how it contradicts the parent's statement -- your employment numbers are not directly related to the claim he makes.
No, they can't. They have a port that's shaped like micro USB but has 20 other pins in it and requires adapter cables/docks to use any of the other features, just like Apple does. Many of these "USB" ports even require an adapter to use the USB data lines -- all they can do with a normal USB cord is charge at a low rate (sometimes lower than the in-use power consumption rate).
No, that's for speaker-level audio after the amp. The port on the bottom puts out line-level audio (with no internal volume control), along with video, status lines to detect/inform the power state, data lines so you can read and control the device, and a whole slew of other things that have come and gone throughout the decade-long life of the 30-pin connector. It is possible to do most of these things with other standard ports (though not all of them, particularly on a thin case), but the replacement is not as simple as power + headphones.
Let me know when your USB port has serial, audio, and video connectors.
You can argue that it's better to have a whole slew of other connectors -- and in many (but not all) cases I'd agree -- but you can't argue that USB is replacement for the dock port (new or old).
You're welcome to not like having a managed media library. Or you could argue that the management bit should be integral to the iPod rather than requiring a host. Others will disagree, preferring the extra features of managed library and the lower cost of host-based management. There are arguments for and against each, and different sizes of libraries and usage styles will dictate differing preferences.
But none of that is at all related to licensing or copying. If pirate 14 copies of the same song and slap them into iTunes, it will happily copy them all to your iPod, right along side any music you may have a license for. Or if you don't want to use iTunes you can use Amarok. The music files written to the iPod are not encrypted or restricted in any way that differs from their original state on your computer. The only requirement is that you use something that writes the music files and metadata DB that the iPod expects to find.
There are 2 steps required to copy music off an iPod: 1. Open the folder on the iPod that contains the music files. There are no particular protections on this folder, it's just not advertised. No special software, knowledge of the command line, or other magic is required to access it. 2. Drag this folder into iTunes
That's it. There's no step 3. iTunes will happily copy all music files from the iPod to your local library, reading the tags out of the files themselves to rebuild the metadata DB and organizing the files in your library into artist and album folders as it goes. It's a bit slow, but it works just fine and it's something that most computer users -- including a 7-year-old -- could do just by reading a list of instructions.
You think the iPod has bad analog audio, listen to the of a Droid III some time. The noise floor is so high it's absolutely unusable at low volumes. I had to switch to BlueTooth just to be able to use the thing at night at reasonable volumes.
But at some point in this process the actual obligations held by textdrive would be subject to settlement as part of bankruptcy/dissolution, and as creditors for who the textdrive has valid contact information the contract holders would need to be notified of those proceedings to make their claims. They might not get any money out of it, but they'd at least get notice of the default.
But we're not talking about physical assets, we're talking about service contracts. If you assumed Joe Plumber's service contracts -- as evidenced in part of the continuation of service under those contracts -- you would be obligated by the same terms of the original contract. Alternatively it would be possible for Joe Plumber to cancel his contracts under whatever terms where therein allowed before dissolving his business, or to enter bankruptcy/dissolution and allow the contracts to be settled as part of those proceedings. But it's not possible for Sam's Pipes to assume the contracts for a while, somehow protect those contracts from bankruptcy/dissolution actions against Joe Plumber during that time, and them simply decide to stop servicing the contracts at some point in the future -- the other parties to the contracts still have claims against whatever legal entity holds responsibility for the contracts.
Use of radio (or other shared infrastructure) is not equivalent to broadcasting. Cell phone communications are, by law, only allowed between the service provider tower and the subscriber handset and a nontrivial effort is taken to secure that unicast communication against eavesdropping.
Unless the rover is unlikely all other space systems from the past half century it has a secondary, low-level computer that can control the power systems, read/write the permanent storage of the primary computer, talk on the omnidirectional antenna, etc. It's similar to remote management systems for servers in lights-out facilitates. That system has its own very-simple OS and CPU that are not tied to the primary system or its updates. In normal operation that system is in standby, but it has watchdogs that will trigger it to take over from the primary under certain conditions. If there's any provision to update that system it would include a permanent, baked-in firmware for fallback if the update went poorly -- like the backup-BIOS jumper you see on some motherboards, except automatically triggered.
Is there some benefit to pubkey over simpler symmetric encryption systems, given that NASA was in a position to do a secure key exchange before the rover left?
Isn't that what's happening? The question doesn't say "I want no-cost accounting software" it says "I want open-source accounting software". Do you have some insight about the submitter to know that he doesn't intend to pay for software and/or support?
If the information is common to everyone with the same implant is it, by definition, not personally identifiable or private health information. Disclosing the existence of patient Q to patient R, or visa versa, would be a violation. But merely telling either of both of them independently that they have their implant set to "Mode B" is not, just as telling patient Q that he has a heart rate of 79 is not a violation if patient R happens to also have a heart rate of 79.
Also, even if there is some private data that needs to be hidden, it's entirely possible to design a crypto system that's secure against known-plaintext attacks. Almost are modern crypto systems are; you'd have to do something dumb to not get that feature from any common crypto library.
Slashdot Mirror
Or they could store more than one hardware fingerprint, just like you can have more than one key in your authorized_keys file.
You're confusing phone numbers with phone service. That's like confusing IP addresses with Internet service. Often they come together, and service providers can be dumb about letting consumers decouple them, but from a technical perspective there's no reason they need to have a 1:1 correlation.
If you've got a lock made in the last say, 50 years, and it's installed correctly, you can't open it with a credit card. Take a look at the latch of your exterior door and you'll see it's split into two independently moving parts. When the small part on the back of the latch is depressed -- as it should be when the door is closed -- the large portion of the latch cannot be moved except by turning the handle. This is intended specifically to defeat the slide-from-inside-to-out attack.
That doesn't stop someone from using any of the other viable attacks on standard doorknob locks, or just breaking a window or the like, but it does keep people from opening your door with a credit card.
Actually many hotspots *do* require you to use the local DNS server. It's pretty trivial, since that's part of the DHCP config, so it's not like end-users have to do anything to make that work. In those cases your data needs to be close enough to the DNS protocol to get propagated upstream, which is basically what iodine does.
Also note the SSH more or less requires TCP, so even if you allowed port 53 outbound you could limit access to the UDP protocol and effectively block SSH and many other tunneling tools, even if they are set to port 53. No DPI required. Sure, you'll prevent TCP DNS queries but that's rarely an issue of the kind of devices connecting to semi-open hotspots, particularly in the pre-payment phase of the connection.
I'm all for standard connectors, but could we *please* stop pretending that Apple iDevice connector is equivalent in functionality to USB?
Dropbox, or any other file sync utility, will happily transfer things between your phone and other computers anytime you're connected to the Internet. Which presumably on a smartphone is essentially constantly. Why you'd ever hassle with manual transfers confuses me.
Is it somehow easier to verify identities outside the Internet? Do you have an in-person identity verification system? Why are you sharing it?
You're assuming the purpose of the list is to catch terrorists. As you note it's probably worthless for that. But it's a great tool for harassing the citizenry, justifying government spending, etc.
That's not true at all. The X25 drives from Intel were terrible in terms of safe writes. The newer Intel drives are better, but only because they added a capacitor to allow in-process writes to complete -- simply being solid-state does not resolve these issues, and in some cases can make them much worse.
You don't need to support your statement. But you do need to explain how it contradicts the parent's statement -- your employment numbers are not directly related to the claim he makes.
So you still need a proprietary, external (and in this case, expensive) adapter to use their ports. How is that different than Apple?
No, they can't. They have a port that's shaped like micro USB but has 20 other pins in it and requires adapter cables/docks to use any of the other features, just like Apple does. Many of these "USB" ports even require an adapter to use the USB data lines -- all they can do with a normal USB cord is charge at a low rate (sometimes lower than the in-use power consumption rate).
No, that's for speaker-level audio after the amp. The port on the bottom puts out line-level audio (with no internal volume control), along with video, status lines to detect/inform the power state, data lines so you can read and control the device, and a whole slew of other things that have come and gone throughout the decade-long life of the 30-pin connector. It is possible to do most of these things with other standard ports (though not all of them, particularly on a thin case), but the replacement is not as simple as power + headphones.
Let me know when your USB port has serial, audio, and video connectors.
You can argue that it's better to have a whole slew of other connectors -- and in many (but not all) cases I'd agree -- but you can't argue that USB is replacement for the dock port (new or old).
You're welcome to not like having a managed media library. Or you could argue that the management bit should be integral to the iPod rather than requiring a host. Others will disagree, preferring the extra features of managed library and the lower cost of host-based management. There are arguments for and against each, and different sizes of libraries and usage styles will dictate differing preferences.
But none of that is at all related to licensing or copying. If pirate 14 copies of the same song and slap them into iTunes, it will happily copy them all to your iPod, right along side any music you may have a license for. Or if you don't want to use iTunes you can use Amarok. The music files written to the iPod are not encrypted or restricted in any way that differs from their original state on your computer. The only requirement is that you use something that writes the music files and metadata DB that the iPod expects to find.
There are 2 steps required to copy music off an iPod:
1. Open the folder on the iPod that contains the music files. There are no particular protections on this folder, it's just not advertised. No special software, knowledge of the command line, or other magic is required to access it.
2. Drag this folder into iTunes
That's it. There's no step 3. iTunes will happily copy all music files from the iPod to your local library, reading the tags out of the files themselves to rebuild the metadata DB and organizing the files in your library into artist and album folders as it goes. It's a bit slow, but it works just fine and it's something that most computer users -- including a 7-year-old -- could do just by reading a list of instructions.
You think the iPod has bad analog audio, listen to the of a Droid III some time. The noise floor is so high it's absolutely unusable at low volumes. I had to switch to BlueTooth just to be able to use the thing at night at reasonable volumes.
Science advances one funeral at a time.
But at some point in this process the actual obligations held by textdrive would be subject to settlement as part of bankruptcy/dissolution, and as creditors for who the textdrive has valid contact information the contract holders would need to be notified of those proceedings to make their claims. They might not get any money out of it, but they'd at least get notice of the default.
But we're not talking about physical assets, we're talking about service contracts. If you assumed Joe Plumber's service contracts -- as evidenced in part of the continuation of service under those contracts -- you would be obligated by the same terms of the original contract. Alternatively it would be possible for Joe Plumber to cancel his contracts under whatever terms where therein allowed before dissolving his business, or to enter bankruptcy/dissolution and allow the contracts to be settled as part of those proceedings. But it's not possible for Sam's Pipes to assume the contracts for a while, somehow protect those contracts from bankruptcy/dissolution actions against Joe Plumber during that time, and them simply decide to stop servicing the contracts at some point in the future -- the other parties to the contracts still have claims against whatever legal entity holds responsibility for the contracts.
Use of radio (or other shared infrastructure) is not equivalent to broadcasting. Cell phone communications are, by law, only allowed between the service provider tower and the subscriber handset and a nontrivial effort is taken to secure that unicast communication against eavesdropping.
Unless the rover is unlikely all other space systems from the past half century it has a secondary, low-level computer that can control the power systems, read/write the permanent storage of the primary computer, talk on the omnidirectional antenna, etc. It's similar to remote management systems for servers in lights-out facilitates. That system has its own very-simple OS and CPU that are not tied to the primary system or its updates. In normal operation that system is in standby, but it has watchdogs that will trigger it to take over from the primary under certain conditions. If there's any provision to update that system it would include a permanent, baked-in firmware for fallback if the update went poorly -- like the backup-BIOS jumper you see on some motherboards, except automatically triggered.
Is there some benefit to pubkey over simpler symmetric encryption systems, given that NASA was in a position to do a secure key exchange before the rover left?
Isn't that what's happening? The question doesn't say "I want no-cost accounting software" it says "I want open-source accounting software". Do you have some insight about the submitter to know that he doesn't intend to pay for software and/or support?
If the information is common to everyone with the same implant is it, by definition, not personally identifiable or private health information. Disclosing the existence of patient Q to patient R, or visa versa, would be a violation. But merely telling either of both of them independently that they have their implant set to "Mode B" is not, just as telling patient Q that he has a heart rate of 79 is not a violation if patient R happens to also have a heart rate of 79.
Also, even if there is some private data that needs to be hidden, it's entirely possible to design a crypto system that's secure against known-plaintext attacks. Almost are modern crypto systems are; you'd have to do something dumb to not get that feature from any common crypto library.