Perhaps merging a PGP-like web of trust interlink with SSL security. So, if a close friend trusts foo.com as a CA, then the Web browser would assume that.
Too easy to infiltrate and subvert. Also, how do you know your friend is who they claim they are? A better solution would be that when you setup your bank's online access you generate a key pair and attach the public key to the 'submit' button (or equivalent). The browser associates the private key with the URL and whenever you login in the future the bank presents proof that it knows your public key. Or it could use it to protect the SSL key exchange (to thwart MITM attacks). None of this is particularly complicated and would really just require extending the JS DOM and making a few protocol tweaks (and their implementations, of course). If you want to access your bank from a different computer you copy over the private key, similar to SSH. Note that this wouldn't be in lieu of user+pass or SSL, but in addition.
So don't give users the lock icon, and just pretend it's an unencrypted website.
Self-signed certificates provide no protection against MITM attacks, but they do provide protection against passive snooping which is what the parent is talking about. There is zero disadvantage to using them.
I agree. It's worth adding that CA-signed certs provide zero protection against MITM attacks as well - it's trivial to proxy to the real site, watch the key exchange, and record the session. Don't even have to bother creating a fake bank site.
The problem is not what the default password is. It could be blank and still not significantly affect the security of the device. Its the admins that don't change the default password that are to blame. Lets face it, even if they ship the next device with a 16 char mixed case, special character, number containing, sufficiently random password, it will still be the default password.
It could have a randomly generated password printed on the same sticker as the serial number and phy mac.
I held the dog's paw.I held it's paw. oops, wrong!
That's not such a great example - 'dog' is a noun, 'it' is a pronoun. 'he' is also a pronoun. English like most languages has highly irregular pronouns, so it should come as no surprise that 'it' is as well. Me/me/mine, he/him/his, it/it/its, her/her/hers, they/them/theirs. A teacher really shouldn't have great difficulty getting this across - just start early and insist on pronouns being used correctly.
Ha. Unlike CERN, they had the insight to build this thing inside an building that isn't in France. That means it is 99.999% proof against a pidgeon dropping a baguette in it.
DoHS memo: All Agents: remain vigilant and on the lookout for foreign parties attempting to corner local bagel markets while purchasing suspicious quantities of whitefish. End memo.
I could easily see myself having one of these in a stand on my night table as a fancy alarm clock. I like to go make coffee and breakfast, then bring it back to bed with a laptop - to check the news, mail, ical (to see what meetings I have), and so forth. Nothing I really need a whole laptop for. The iPhone can do the same but is a bit small... I need glasses to read text on it.
Correct me if I'm wrong, but wouldn't this result in asymmetric inflation? (E.g. if it's donut shaped and inflation is really a gravitational collapse of the hole.)
How hard is it to find an editor that will handle TABS nicely?
It's not just about editors, but about terminal windows as well. Just such a simple command as "svn diff file.c | more" will indent at 8 stop tabs, causing unreadable wrapping. The problem is everything from Terminal.app (or gnome-terminal or whatever you use) to 'more', to diff vewiers, web svn tree browsers, trac, post-commit email, etc, has to be made aware of non-8 stop tabs and keep your individual preference. This is turn adds a need for login (or navigation options) - and just adds bloat and complexity for something that has a very simple solution: use spaces.
Wouldn't drinking milk resolved the Vitamin D deficiency.
In the case of Rickets in the US and Europe it occurs predominantly among immigrants who have moved there from parts of the world closer to the equator. See e.g. http://www.eje-online.org/cgi/content/abstract/EJE-08-0818v1 . They're cold during much of the year so cover up virtually all their skin, have pigmentation that requires more exposure for the same Vitamin D generation, and are frequently lactose intolerant. Some percentage is due to hereditary metabolic disorders.
I agree. A good manager should also be able to recognize what areas they don't understand and then assemble a group of people to advise & teach her/him on the details of the specific industry or company.
The problem is when you do this you get a business run by committee. You really do need managers who are strong in their field of business, but also smart and skilled when it comes to business strategy and deal making. Otherwise they can't come up with winning ideas to capitalize on a moment of opportunity - they likely won't even recognize it and it just floats past. This is how most business happens, and it takes a certain type of person to be successful at it. But if they don't have deep, internalized understanding of their business this just won't happen. Businesses run by committee almost always give a particular impression of appearing to drift about aimlessly.
Of course it does, because the HDMI signal is 165MHz+ (HDMI 1.0, later added higher modes). It matters for two digital devices to talk to each other, but there's no way a human could recognize picosecond jitter in the decoded video or audio which runs in kilohertz for audio and hertz for video.
HDMI isn't clock jitter prone though since it's fixed to a negotiated rate. The audio component, if I remember correctly (I haven't looked at HDMI in a few years) is packetized between video lines (or is it frames, I forget) in a negotiated format, transmitted at the video clock rate. The rate has to stay within some fraction of sample period or the receiver loses sync. (Resulting in a momentary flicker as it resyncs.)
In SPDIF the rate isn't fixed but has to fall within tolerances. There is no fixed clock; instead it's inferred from looking at the data stream (each bit makes two transitions for this purpose). The purpose of Denon Link (which works just fine with a $3 UTP cable from monoprice.com, guaranteed) is to extend SPDIF to more than two channels.
That doesn't apply to digital data. If a 1 is sent and is received as a "0.8" or a "1.2", it will still be interpreted as a 1.
This is not the issue with SPDIF. SPDIF has a variable data rate and the clock is embedded in the modulation. The source can (and will!) vary its transmission rate. The model is that you have a mechanical CD transport that reads bits off a disk, sending them down a wire as they're decoded. Because the transport is physical its actual rotational speed will vary. The disks also vary (within tolerances) in density on the disk itself; the drive mechanism is PLL locked to the disk contents, not a master clock. If the pits on the disk get denser it slows down a bit, when they get sparser it speeds up.
This model is called streaming. When A/V engineers talk about streamed data, like an Elementary Stream (ES), this is what they mean. MPEG-2 is also a streamed model for instance; if you read the specs you'll find bounds and tolerances on data rates, intermediate buffers, jitter, etc. It's how the standards are created. They're not anything resembling IP datagrams, the closest you'll get to that is transport streams which basically packetize and mux multiple elementary streams into a transport stream. The reason the models are created like this is that audio and video generally and sent down completely independent paths and need to retain the their sync. Or at least that was the reasoning when the standards were created, these days it's mostly just a pain in the rear.
If you run two self-clocked signals at variable rates down two wires of different lengths, the receiver will see the bitstreams arrive at a slight skew. Since they're both variable rate to begin with it's no trivial problem to try to heuristically determine when the bits were actually sent, or read off the disk, or were meant to be read of the disk when it was mastered. The issue isn't whether the clocks will be off, but whether it's audible.
Slashdot Mirror
Perhaps merging a PGP-like web of trust interlink with SSL security. So, if a close friend trusts foo.com as a CA, then the Web browser would assume that.
Too easy to infiltrate and subvert. Also, how do you know your friend is who they claim they are? A better solution would be that when you setup your bank's online access you generate a key pair and attach the public key to the 'submit' button (or equivalent). The browser associates the private key with the URL and whenever you login in the future the bank presents proof that it knows your public key. Or it could use it to protect the SSL key exchange (to thwart MITM attacks). None of this is particularly complicated and would really just require extending the JS DOM and making a few protocol tweaks (and their implementations, of course). If you want to access your bank from a different computer you copy over the private key, similar to SSH. Note that this wouldn't be in lieu of user+pass or SSL, but in addition.
So don't give users the lock icon, and just pretend it's an unencrypted website.
Self-signed certificates provide no protection against MITM attacks, but they do provide protection against passive snooping which is what the parent is talking about. There is zero disadvantage to using them.
I agree. It's worth adding that CA-signed certs provide zero protection against MITM attacks as well - it's trivial to proxy to the real site, watch the key exchange, and record the session. Don't even have to bother creating a fake bank site.
The problem is not what the default password is. It could be blank and still not significantly affect the security of the device. Its the admins that don't change the default password that are to blame. Lets face it, even if they ship the next device with a 16 char mixed case, special character, number containing, sufficiently random password, it will still be the default password.
It could have a randomly generated password printed on the same sticker as the serial number and phy mac.
I held the dog's paw. I held it's paw. oops, wrong!
That's not such a great example - 'dog' is a noun, 'it' is a pronoun. 'he' is also a pronoun. English like most languages has highly irregular pronouns, so it should come as no surprise that 'it' is as well. Me/me/mine, he/him/his, it/it/its, her/her/hers, they/them/theirs. A teacher really shouldn't have great difficulty getting this across - just start early and insist on pronouns being used correctly.
Ha. Unlike CERN, they had the insight to build this thing inside an building that isn't in France. That means it is 99.999% proof against a pidgeon dropping a baguette in it.
DoHS memo: All Agents: remain vigilant and on the lookout for foreign parties attempting to corner local bagel markets while purchasing suspicious quantities of whitefish. End memo.
I could easily see myself having one of these in a stand on my night table as a fancy alarm clock. I like to go make coffee and breakfast, then bring it back to bed with a laptop - to check the news, mail, ical (to see what meetings I have), and so forth. Nothing I really need a whole laptop for. The iPhone can do the same but is a bit small... I need glasses to read text on it.
I'll counter your "costs money"
1. GM did it in the Cobalt with basically the same engine. What does the Saab 2.0T need to produce over 300hp?
Wouldn't this require a different gearbox, clutch assembly, body stiffness, and rear suspension? Maybe generally beefier engine supports?
Correct me if I'm wrong, but wouldn't this result in asymmetric inflation? (E.g. if it's donut shaped and inflation is really a gravitational collapse of the hole.)
How hard is it to find an editor that will handle TABS nicely?
It's not just about editors, but about terminal windows as well. Just such a simple command as "svn diff file.c | more" will indent at 8 stop tabs, causing unreadable wrapping. The problem is everything from Terminal.app (or gnome-terminal or whatever you use) to 'more', to diff vewiers, web svn tree browsers, trac, post-commit email, etc, has to be made aware of non-8 stop tabs and keep your individual preference. This is turn adds a need for login (or navigation options) - and just adds bloat and complexity for something that has a very simple solution: use spaces.
Wouldn't drinking milk resolved the Vitamin D deficiency.
In the case of Rickets in the US and Europe it occurs predominantly among immigrants who have moved there from parts of the world closer to the equator. See e.g. http://www.eje-online.org/cgi/content/abstract/EJE-08-0818v1 . They're cold during much of the year so cover up virtually all their skin, have pigmentation that requires more exposure for the same Vitamin D generation, and are frequently lactose intolerant. Some percentage is due to hereditary metabolic disorders.
I agree. A good manager should also be able to recognize what areas they don't understand and then assemble a group of people to advise & teach her/him on the details of the specific industry or company.
The problem is when you do this you get a business run by committee. You really do need managers who are strong in their field of business, but also smart and skilled when it comes to business strategy and deal making. Otherwise they can't come up with winning ideas to capitalize on a moment of opportunity - they likely won't even recognize it and it just floats past. This is how most business happens, and it takes a certain type of person to be successful at it. But if they don't have deep, internalized understanding of their business this just won't happen. Businesses run by committee almost always give a particular impression of appearing to drift about aimlessly.
Of course it does, because the HDMI signal is 165MHz+ (HDMI 1.0, later added higher modes). It matters for two digital devices to talk to each other, but there's no way a human could recognize picosecond jitter in the decoded video or audio which runs in kilohertz for audio and hertz for video.
HDMI isn't clock jitter prone though since it's fixed to a negotiated rate. The audio component, if I remember correctly (I haven't looked at HDMI in a few years) is packetized between video lines (or is it frames, I forget) in a negotiated format, transmitted at the video clock rate. The rate has to stay within some fraction of sample period or the receiver loses sync. (Resulting in a momentary flicker as it resyncs.)
In SPDIF the rate isn't fixed but has to fall within tolerances. There is no fixed clock; instead it's inferred from looking at the data stream (each bit makes two transitions for this purpose). The purpose of Denon Link (which works just fine with a $3 UTP cable from monoprice.com, guaranteed) is to extend SPDIF to more than two channels.
That doesn't apply to digital data. If a 1 is sent and is received as a "0.8" or a "1.2", it will still be interpreted as a 1.
This is not the issue with SPDIF. SPDIF has a variable data rate and the clock is embedded in the modulation. The source can (and will!) vary its transmission rate. The model is that you have a mechanical CD transport that reads bits off a disk, sending them down a wire as they're decoded. Because the transport is physical its actual rotational speed will vary. The disks also vary (within tolerances) in density on the disk itself; the drive mechanism is PLL locked to the disk contents, not a master clock. If the pits on the disk get denser it slows down a bit, when they get sparser it speeds up.
This model is called streaming. When A/V engineers talk about streamed data, like an Elementary Stream (ES), this is what they mean. MPEG-2 is also a streamed model for instance; if you read the specs you'll find bounds and tolerances on data rates, intermediate buffers, jitter, etc. It's how the standards are created. They're not anything resembling IP datagrams, the closest you'll get to that is transport streams which basically packetize and mux multiple elementary streams into a transport stream. The reason the models are created like this is that audio and video generally and sent down completely independent paths and need to retain the their sync. Or at least that was the reasoning when the standards were created, these days it's mostly just a pain in the rear.
If you run two self-clocked signals at variable rates down two wires of different lengths, the receiver will see the bitstreams arrive at a slight skew. Since they're both variable rate to begin with it's no trivial problem to try to heuristically determine when the bits were actually sent, or read off the disk, or were meant to be read of the disk when it was mastered. The issue isn't whether the clocks will be off, but whether it's audible.
Totally. Used Cisco gear is cheap on ebay.
That will be the Xbox\370.