This could extend to companies doing business with the Russian government. It's not so far-fetched in any country. The Defense Department in the US is putting a great deal of pressure on its suppliers to get up to speed with IPv6, with suggestions that some of those who fail to do so will find themselves without contracts. Russia could require that at least some systems connecting with government computers be running the official version of Linux.
It's not for the whole country, but then, the KGB didn't have to have a personal spy in every room to keep the people's heads down in fear. A number of smaller projects sufficed to collect the information deemed necessary to maintain control.
I don't know how you find stations that don't have ads. Those that do in the places I live and visit are religious, and that's it. Even the NPR-affiliated stations have ads, though they don't call them that. They're 15-second soundbites read by station personnel, but they reference often-corporate contributors, their slogans, products and events, and where to buy the products or tickets. The local Pacifica affiliate doesn't have ads per se, but they do basically beg the entire year for money, which is about as bad.
Ads are not generally based on pageviews, but adviews. The ads are, to provide a simplified explanation, loaded from a URL specific to the site (for tracking purposes). If the ad is never loaded, no increase to the adview is made, and the site owner doesn't see income from that pageview.
An exoskeleton sits outside of your body and provides support and usually amplification for whatever you undertake. It doesn't require protecting the user, and such armor would be pointless excess weight for someone who is simply moving weight that would normally take several people or otherwise-awkward equipment.
I agree that the article shows a walker. But something like what Ripley had in Aliens and which has provided inspiration to a number of recent advances was definitely an exoskeleton, and it provided very little protection other than against dropped containers via a rollcage.
The craftspeople working on those high-end mansions are also the masters who oversee and train the journeymen. It is the responsibility of the masters to push the limits of the craft, and one of the ways to do so is to work on projects paid for by people who want something at or beyond the current limits of the craft.
The celebration of Christmas was not originally about Christianity. It was absorbed into the Christian faith in part as a means of converting those that celebrated the solstice. Jesus was not born in the winter, but sometime when the shepherds were still in the fields with their flocks (Luke 2:8, "And there were in the same country shepherds abiding in the field, keeping watch over their flock by night"), which is spring through autumn.
The sentiment of feasting and celebrating family around the time of the solstice is much older than Christmas.
In addition, for some things, starting on a GUI for general work and then getting used to the command line for certain larger-scale operations is also good. The firewalls we have at work are very good, and the GUI is simply a front-end for the CLI, but the learning curve for both is fairly steep, much more so for the CLI. I have found it much easier to get new admins up on the GUI and then introduce them to the CLI one job at a time until they get the syntax (which is fairly uniform).
There is something else which GUIs can excel at over CLIs, though it depends on the design of each. When zipping through huge volumes of logs, I prefer to have the GUI scroll it past at volume-appropriate speeds because the columns are much more neatly laid out and I can spot general patterns more easily. Less-common items do require me to either use finer filters or to move to the CLI where I can make use of grep, sort, and awk, but the flexibility of those options is highly preferable over a simple CLI output that does not provide contextual coloring or other useful aids.
Social Security is in the red for the first time ever.
For the first time in nearly 30 years, the system will pay out more benefits than it receives in payroll taxes both this year and next, the government officials who oversee Social Security said on Thursday.
And while Social Security cash flow will likely head back into the black for a few years after that, starting in 2015 it looks to stay in the red for the long haul, the trustees said in their annual report.
The military wants (and arguably needs) another carrier or two, especially since the Enterprise is due for decommissioning in a few years. But the military does not want more F-22s, and would rather slice away a few ships, some aircraft, and some ground vehicles. I'm betting that the Pentagon has a better idea of what works in combat than a random set of senators. It wouldn't solve the deficit, but a billion here and a billion there, and pretty soon we're talking about real money.
China didn't actually say that it wanted a unified Korea under Seoul's control. What it said was that it didn't mind the idea, but also was OK with North Korea being there as a buffer state.
China's leadership seems OK with the status quo, largely because it defers having to deal with a few million people rushing across its border terrified that the South Korea military is about to skewer and eat them alive. South Korea is OK with the status quo for right now because it doesn't want to foot the trillion-dollar cost of unification.
But does that violate US law or Swiss law? If there's no US law against importing such merchandise, the appropriate action should be to file suit in Switzerland.
It depends on what the code's author does with it. If I code up something that is harmful and submit it to Metasploit or OpenVAS, they accept it if it works and I get some credit. It can clearly be used for evil, and yet it will be gladly accepted.
Consider the FBI's malware that was discussed a few years ago. If the FBI, operating with a warrant, convinces a target to download and install it, or uses a known bug in the target's software to install it, and then uses the capabilities of the malware to spy on the target. That's legitimate, and yet it's not code that we want on our systems (targets or not).
I looked up a little more on this case in particular. Costco bought the watches from a New York-based company that bought them from people that had bought them from authorized distributors. Omega contends that the initial purchaser was not authorized to resell or import them to the United States, so any subsequent sale was unauthorized and hence illegal. Omega brought suit on the basis of control of the Omega logo.
This troubles me not so much as an issue of first sale doctrine (though there is that), but as an expansion of copyright law. A logo should be treated as a trademark, and reasonable control should be provided over its use. However, restricting sale based on ownership and control of the trademark under copyright law seems a ludicrous expansion of powers of creative ownership.
I also take issue with the 9th Circuit's jurisdiction argument. The Court explicitly expands the scope of the presumption of extraterritoriality, whereby US law applies to undertakings in the US and not elsewhere, unless specifically indicated in the law. I see nothing wrong with Omega asserting control over its trademarks in the US, registered or not, or control over copyright of published materials. However, if no US law was broken in the importation or further sale, jurisdiction doesn't seem like it would be an issue here. If there's any jurisdictional question, it is that Omega should have taken the actions against the people that bought the watches in the first place, filing suits in those nations where a US-style first-sale doctrine does not apply, or perhaps against the authorized distributors that were selling watches far enough below MSRP that the initial buyer and the NY-based importer and Costco could all profit from the endeavor.
We'll have to wait and see what happens in other districts, since the Court issued only a per curiam slip opinion affirming the 9th Circuit's decision. This is as bad a decision as I have seen in recent years short of Kelso.
Yeah, to charge warrantless wiretapping they would have to find evidence the backdoor was actually used without a warrant. Besides which, why would the US gov't charge its own agents for working on its behalf? GP makes no sense on this point.
If evidence was found that it was used without a warrant, the same thing that happens in all cases would happen: evidence derived from it, or the fruit of such evidence, would be thrown out of court.
Given the OS, I don't expect that this would be used widely by terrorists (I could be wrong). This is more likely to be used in corporate or perhaps individual environments, and so the evidence is more likely to be used in court.
How is it a bribe? They reportedly paid someone to do something that wasn't against the law or a violation of someone's responsibilities. I'm still not seeing where any legal issues arise.
If it is true, it was submitted as source code, subject to review, accepted by the community, and installed by users. I see nothing illegal here.
I also don't see where it's necessarily warrantless wiretapping. Sure, it could be used for that, but this kind of thing could also absolutely be used for warranted wiretapping. The FBI goes to a judge, gets a warrant, captures the traffic, and decrypts it using the backdoor. Again, nothing illegal.
There are ethical issues with intentionally subverting such a project, but I don't see legal issues such as you claim.
Before you go all tinfoil-hat on us, maybe you should get some points straight. Among them is that the Detroit idea is a proposal, is contingent on approvals at multiple levels and securing funding to move people from neighborhoods that would no longer receive full services, and is simply reflective of the reality that Detroit, once a bustling city of 1.85 million people in 1950, is now under half of that, with nearly 35,000 empty homes.
Besides, urbanization has been happening for centuries. It's picked up the pace in recent decades, but I bet most of the people around in even the 1950s would have been hard pressed to provide entirely for themselves had the need arisen.
I propose an amendment to the Constitution prohibiting those in any position of authority in the federal government, to include at a minimum any person who is elected or subject to constitutional confirmation procedures but also those designated by Congress, to be prohibited from working in the private sector in any position of influence or interaction related to their old job, directly or indirectly, for a period of not less than five years, with Congress authorized to extend but not reduce the term by law. Hence, senior members of DHS would not be allowed to work for airline security companies, senior members of the DoD would not be allowed to work for defense contractors, etc, and neither would they be allowed to contract, consult, or advise such companies.
That may well be true -- djb is one of the smartest guys out there -- but if he hasn't provided the proof to either NIST or the Skein team, it shouldn't really factor into the results.
SHA-1 was not "cracked." A weakness was found in it that reduced the strength by 2^11 to 2^69 instead of 2^80 when conducting preimage attacks. Even on specialized hardware, this is not a practical attack, requiring thousands of years to come up with a message that hashes to the same value. Papers since then have found variations on the weakness, but they have only been demonstrated in reduced-round variants of SHA-1, not in full implementations due to the processing power required.
The weakness was recognized as a potential problem, hence the recommended move to SHA-2, particularly the stronger variants of it. The SHA-3 competition was born out of concern that SHA-2 could suffer from similar weaknesses, which may doom the SHA-3 contestants that draw from SHA-2 at a political level if not a technical level.
This reminds me of the TCAS (Traffic Collision Avoidance System) in some of the more advanced planes. I get a screen that tells me where known traffic is, and in areas with good radar coverage like the Los Angeles Basin, it's useful enough that I don't want to fly a plane that doesn't have it. While it's seen as tempting to rely on it alone to avoid traffic, it generally isn't used that way, and in fact, I've used it to locate traffic that otherwise isn't easily visible (a white Cessna against a hazy blue-white sky is tough to pick out at a range of three miles or more).
It doesn't remove the pilot's responsibility to keep an eye on what's going on outside, but it still instills a sense of safety and control that isn't as common in an analog aircraft.
The article mentions that the concept currently works only on the driver's side. The passenger side works differently, and the inventor hasn't found a solution yet, or at least as of the publishing of that article.
Slashdot Mirror
This could extend to companies doing business with the Russian government. It's not so far-fetched in any country. The Defense Department in the US is putting a great deal of pressure on its suppliers to get up to speed with IPv6, with suggestions that some of those who fail to do so will find themselves without contracts. Russia could require that at least some systems connecting with government computers be running the official version of Linux.
It's not for the whole country, but then, the KGB didn't have to have a personal spy in every room to keep the people's heads down in fear. A number of smaller projects sufficed to collect the information deemed necessary to maintain control.
I don't know how you find stations that don't have ads. Those that do in the places I live and visit are religious, and that's it. Even the NPR-affiliated stations have ads, though they don't call them that. They're 15-second soundbites read by station personnel, but they reference often-corporate contributors, their slogans, products and events, and where to buy the products or tickets. The local Pacifica affiliate doesn't have ads per se, but they do basically beg the entire year for money, which is about as bad.
Ads are not generally based on pageviews, but adviews. The ads are, to provide a simplified explanation, loaded from a URL specific to the site (for tracking purposes). If the ad is never loaded, no increase to the adview is made, and the site owner doesn't see income from that pageview.
An exoskeleton sits outside of your body and provides support and usually amplification for whatever you undertake. It doesn't require protecting the user, and such armor would be pointless excess weight for someone who is simply moving weight that would normally take several people or otherwise-awkward equipment.
I agree that the article shows a walker. But something like what Ripley had in Aliens and which has provided inspiration to a number of recent advances was definitely an exoskeleton, and it provided very little protection other than against dropped containers via a rollcage.
The craftspeople working on those high-end mansions are also the masters who oversee and train the journeymen. It is the responsibility of the masters to push the limits of the craft, and one of the ways to do so is to work on projects paid for by people who want something at or beyond the current limits of the craft.
The celebration of Christmas was not originally about Christianity. It was absorbed into the Christian faith in part as a means of converting those that celebrated the solstice. Jesus was not born in the winter, but sometime when the shepherds were still in the fields with their flocks (Luke 2:8, "And there were in the same country shepherds abiding in the field, keeping watch over their flock by night"), which is spring through autumn.
The sentiment of feasting and celebrating family around the time of the solstice is much older than Christmas.
Or a central firewall manager. I'll take that over a bunch of individual firewalls.
In addition, for some things, starting on a GUI for general work and then getting used to the command line for certain larger-scale operations is also good. The firewalls we have at work are very good, and the GUI is simply a front-end for the CLI, but the learning curve for both is fairly steep, much more so for the CLI. I have found it much easier to get new admins up on the GUI and then introduce them to the CLI one job at a time until they get the syntax (which is fairly uniform).
There is something else which GUIs can excel at over CLIs, though it depends on the design of each. When zipping through huge volumes of logs, I prefer to have the GUI scroll it past at volume-appropriate speeds because the columns are much more neatly laid out and I can spot general patterns more easily. Less-common items do require me to either use finer filters or to move to the CLI where I can make use of grep, sort, and awk, but the flexibility of those options is highly preferable over a simple CLI output that does not provide contextual coloring or other useful aids.
Social Security is in the red for the first time ever.
http://money.cnn.com/2010/08/05/news/economy/social_security_trustees_report/index.htm
The military wants (and arguably needs) another carrier or two, especially since the Enterprise is due for decommissioning in a few years. But the military does not want more F-22s, and would rather slice away a few ships, some aircraft, and some ground vehicles. I'm betting that the Pentagon has a better idea of what works in combat than a random set of senators. It wouldn't solve the deficit, but a billion here and a billion there, and pretty soon we're talking about real money.
China didn't actually say that it wanted a unified Korea under Seoul's control. What it said was that it didn't mind the idea, but also was OK with North Korea being there as a buffer state.
China's leadership seems OK with the status quo, largely because it defers having to deal with a few million people rushing across its border terrified that the South Korea military is about to skewer and eat them alive. South Korea is OK with the status quo for right now because it doesn't want to foot the trillion-dollar cost of unification.
But does that violate US law or Swiss law? If there's no US law against importing such merchandise, the appropriate action should be to file suit in Switzerland.
It depends on what the code's author does with it. If I code up something that is harmful and submit it to Metasploit or OpenVAS, they accept it if it works and I get some credit. It can clearly be used for evil, and yet it will be gladly accepted.
Consider the FBI's malware that was discussed a few years ago. If the FBI, operating with a warrant, convinces a target to download and install it, or uses a known bug in the target's software to install it, and then uses the capabilities of the malware to spy on the target. That's legitimate, and yet it's not code that we want on our systems (targets or not).
It all depends on the intent and the goal.
That is correct. A tie vote sets no precedent.
I looked up a little more on this case in particular. Costco bought the watches from a New York-based company that bought them from people that had bought them from authorized distributors. Omega contends that the initial purchaser was not authorized to resell or import them to the United States, so any subsequent sale was unauthorized and hence illegal. Omega brought suit on the basis of control of the Omega logo.
This troubles me not so much as an issue of first sale doctrine (though there is that), but as an expansion of copyright law. A logo should be treated as a trademark, and reasonable control should be provided over its use. However, restricting sale based on ownership and control of the trademark under copyright law seems a ludicrous expansion of powers of creative ownership.
I also take issue with the 9th Circuit's jurisdiction argument. The Court explicitly expands the scope of the presumption of extraterritoriality, whereby US law applies to undertakings in the US and not elsewhere, unless specifically indicated in the law. I see nothing wrong with Omega asserting control over its trademarks in the US, registered or not, or control over copyright of published materials. However, if no US law was broken in the importation or further sale, jurisdiction doesn't seem like it would be an issue here. If there's any jurisdictional question, it is that Omega should have taken the actions against the people that bought the watches in the first place, filing suits in those nations where a US-style first-sale doctrine does not apply, or perhaps against the authorized distributors that were selling watches far enough below MSRP that the initial buyer and the NY-based importer and Costco could all profit from the endeavor.
We'll have to wait and see what happens in other districts, since the Court issued only a per curiam slip opinion affirming the 9th Circuit's decision. This is as bad a decision as I have seen in recent years short of Kelso.
If evidence was found that it was used without a warrant, the same thing that happens in all cases would happen: evidence derived from it, or the fruit of such evidence, would be thrown out of court.
Given the OS, I don't expect that this would be used widely by terrorists (I could be wrong). This is more likely to be used in corporate or perhaps individual environments, and so the evidence is more likely to be used in court.
A moral responsibility, yes. But it's not a legal responsibility, so bribery doesn't apply.
How is it a bribe? They reportedly paid someone to do something that wasn't against the law or a violation of someone's responsibilities. I'm still not seeing where any legal issues arise.
If it is true, it was submitted as source code, subject to review, accepted by the community, and installed by users. I see nothing illegal here.
I also don't see where it's necessarily warrantless wiretapping. Sure, it could be used for that, but this kind of thing could also absolutely be used for warranted wiretapping. The FBI goes to a judge, gets a warrant, captures the traffic, and decrypts it using the backdoor. Again, nothing illegal.
There are ethical issues with intentionally subverting such a project, but I don't see legal issues such as you claim.
Before you go all tinfoil-hat on us, maybe you should get some points straight. Among them is that the Detroit idea is a proposal, is contingent on approvals at multiple levels and securing funding to move people from neighborhoods that would no longer receive full services, and is simply reflective of the reality that Detroit, once a bustling city of 1.85 million people in 1950, is now under half of that, with nearly 35,000 empty homes.
Besides, urbanization has been happening for centuries. It's picked up the pace in recent decades, but I bet most of the people around in even the 1950s would have been hard pressed to provide entirely for themselves had the need arisen.
I propose an amendment to the Constitution prohibiting those in any position of authority in the federal government, to include at a minimum any person who is elected or subject to constitutional confirmation procedures but also those designated by Congress, to be prohibited from working in the private sector in any position of influence or interaction related to their old job, directly or indirectly, for a period of not less than five years, with Congress authorized to extend but not reduce the term by law. Hence, senior members of DHS would not be allowed to work for airline security companies, senior members of the DoD would not be allowed to work for defense contractors, etc, and neither would they be allowed to contract, consult, or advise such companies.
That may well be true -- djb is one of the smartest guys out there -- but if he hasn't provided the proof to either NIST or the Skein team, it shouldn't really factor into the results.
SHA-1 was not "cracked." A weakness was found in it that reduced the strength by 2^11 to 2^69 instead of 2^80 when conducting preimage attacks. Even on specialized hardware, this is not a practical attack, requiring thousands of years to come up with a message that hashes to the same value. Papers since then have found variations on the weakness, but they have only been demonstrated in reduced-round variants of SHA-1, not in full implementations due to the processing power required.
The weakness was recognized as a potential problem, hence the recommended move to SHA-2, particularly the stronger variants of it. The SHA-3 competition was born out of concern that SHA-2 could suffer from similar weaknesses, which may doom the SHA-3 contestants that draw from SHA-2 at a political level if not a technical level.
Sometimes more, with picture-in-picture and an analog connection for the low channels.
This reminds me of the TCAS (Traffic Collision Avoidance System) in some of the more advanced planes. I get a screen that tells me where known traffic is, and in areas with good radar coverage like the Los Angeles Basin, it's useful enough that I don't want to fly a plane that doesn't have it. While it's seen as tempting to rely on it alone to avoid traffic, it generally isn't used that way, and in fact, I've used it to locate traffic that otherwise isn't easily visible (a white Cessna against a hazy blue-white sky is tough to pick out at a range of three miles or more).
It doesn't remove the pilot's responsibility to keep an eye on what's going on outside, but it still instills a sense of safety and control that isn't as common in an analog aircraft.
The article mentions that the concept currently works only on the driver's side. The passenger side works differently, and the inventor hasn't found a solution yet, or at least as of the publishing of that article.