Some of that is intentional. For example, they make using a debit card as a credit card difficult because it saves them money. Walmart is the only store I know that labels the button to do so. Sometimes I ask how to do it just to give back a little of the frustration.
It's much more Web 2.0 to create a user interface that's minimal to the point of being cryptic, and to call users that can't figure it out idiots. It also helps to have a complete lack of standards.
There's a lot of room for improvement in programming languages. New features aren't just novelty. The database/language impedance mismatch is still pretty big, language feature to support multithreading are still weak, strongly typed languages still need to handle "dynamic-ness" better. Microsoft has done a great job of introducing new features that people actually want while still maintaining backwards compatibility. Oracle is being way too conservative here and it does matter to their customers - even the big ones.
I spent a lot of time recently working at a fortune 20 company. Java was the official programming language of the company, but the Enterprise Architecture group was starting to lean closer to.Net when I left.
For a language which forced Microsoft to up it's game with C#
Java has been playing catch up with C# for almost ten years. Attributes, generics, and lambdas were all added to Java long after they were added to C#. Also, Microsoft made them part of the runtime, while Java only made them part of the compiler (for the most part), so the features work a lot better in C#.
The point of this article is that Oracle has been slowing down the pace of innovation to an even slower pace than Sun was at, and Sun had already lost a five year head start to Microsoft very quickly.
"runtime and a language with a huge install base" describes a future where Java just coasts. By contrast, Python, Ruby, and.Net are all runtimes and languages (several languages in the case of.Net) with a huge install base that are actively introducing new frameworks, development tools, and feature on a regular basis. I'm calling an interpreter a runtime for the purposes of this conversation.
The number of possible valid credit card numbers is so small that any hashing solution can be brute forced very quickly, even if each record has its own salt. The only protection would be to make the algorithm secret, but then you've just reduced your system to security by obscurity and as soon as someone figures out the algorithm, you're toast.
I wouldn't recommend Office Automation on a server if there is any alternative. For beginners, there's too many gotchas and for advanced users, there's plenty of alternatives that will do what you want without too much difficulty. Office with.Net is especially problematic because the COM components run as out-of-process servers and due to.Net's garbage collection and COM interoperability, they are difficult to get to shut down properly.
In the payment card industry, this is called a token, not a hash. The difference is that a hash can be algorithmically generated from the source material, while a token cannot. Because there is no forward link outside the entity that generated the token to go from card to token, the tokens can be different at each merchant, making a loss of token much less of a problem than a loss of hashes would be. It's also 100% infeasible to break the token generating algorithm since there isn't one. In my experience, tokens are simply generated sequentially (skipping those that don't pass Luhn check). Another beauty of tokens is that they can pass validity checks for credit card numbers, so they can be handed to third-party software and treated just like card numbers, but without the risk of breach.
They implemented it the way they did so they can sell it as a drop-in solution that requires no coding changes. Unfortunately, a security technologies don't matter as much as processes do, so this product, like all other silver-bullet products, will never be all that good.
You mean regular DBAs like the next Edward Snowden? Inside threats are important and are one of the reasons this feature exists. LitchField did what he does best; he showed that the product doesn't quite live up to the marketing material.
How would a hashed credit card number ever be useful? You would have a really hard time sending a request for payment to a payment processor if you did.
They didn't say that. They said that the 40% "dwarfs the number of watchlisted people suspected of ties to al Qaeda, Hamas, and Hezbollah combined". That means that the second list is only a small portion of the remaining 60%. It also means that most of the 60% aren't suspected of having ties to the three groups - and therefore also are probably false positives. Note that they said "suspected", most of the 60% aren't even suspected of having ties to the big three.
It's different because the agencies with security as their middle name don't have a backdoor for this.
That's why I was careful to say "end-to-end encryption" instead of "https". If you aren't using the public CA infrastructure, your data may be private.
Is this article suggesting that new communication paradigms are a bad idea because the security gear optimized for the old paradigm won't work? Should we wait for the security industry to invent multipath TCP? BTW, this is the same security gear that can already be thwarted by end-to-end encryption. How is this any different?
Believe me, this install will never be PCI complaint. Either they will choose a solution that doesn't store cardholder data, or will outsource the credit card processing to someone else. It isn't cost effective to have a PCI compliant installation this small. So, this issue can be ignored when discussing "should a server like this have a firewall?".
Yes, it's legal. But, Southwest's Contract of Carriage lists 13 reasons that boarding can be denied. "We disagree with you" isn't on the list. So, they violated their own contract and they owe the passenger between 200 and 400 percent of the fare, depending on how late he gets to his destination.
Tweet after you land and your family and friends read it. Tweet before you take off and it gets on the front page of Slashdot. I'd say he played it exactly the right way to both get to where he was going and to make as much bad Southwest publicity as possible.
KMart was run into bankruptcy 13 years ago by it's CEO and COO. I don't mean they happened to be there while something bad happened, I mean that business strategy that was chosen directly caused the bankruptcy. The COO was the one making most of the calls and his previous two jobs got rid of him when they went bankrupt (Hechinger, Big V Supermarkets). Yes, he bankrupted three companies in a row. He's still an executive. Also, when he left KMart, he wasn't really fired - he "left voluntarily" and on the way out he was given a 3 million dollar loan and a document that said he would never have to pay back that loan. They did that because they weren't allowed to give him a bonus due the whole Chapter 11 thing and they felt so bad that he was going to be out of a job and needing to live on his meager eight figure investment portfolio.
Isn't this just another form of the "illegal to be black" line of thinking? Just because you have a certain skin color or live in a certain neighborhood doesn't automatically mean you should be treated like a criminal. Sure it's expedient for cops to make these generalizations, but it's wrong.
I would like to have seen the original example as "The city government that maintains the roads and traffic control devices would be liable for allowing the suspect to get away fast enough to evade capture".
Visual Basic went to.Net five versions ago. It was acceptable to take VB to mean classic VB in 2003, but in 2014, you have to say so if you mean the old stuff. The VB6 development environment doesn't even run on any supported operating system. VBA is still around, but it's always been incorrect to refer to VBA as VB.
I think it's interesting that you know Visual Basic, but want to get into C#. My first question would be "Why?". Both run on the same framework and both are equally capable. All you're doing is learning new syntax to do things you already know how to do. After that question is the comment "You pretty much already know C#". Sure, it's a different language from VB, but that's the easy part. It uses the same tools and libraries, so you know 95% of it already.
You are absolutely 100 percent technically correct. But whoever gets their power at hydro rates is the consumer of hydro power. If Robert Moses was shut down, the customers paying the lower rate would either have to pay more or stop receiving power (or the person who wrote the contract would lose money). The people paying coal rates would be easy to serve by bringing power from coal plant at other points on the grid. So, for all intents and purposes, they are getting the power from Robert Moses.
We could extend this process to things like carbon credits and any future non-renewable tax. The providers would only be able to sell a certain quantity of "penalty-exempt" power. That would drive the market for that power, even thought the customer may not receive exactly the electron they paid for. So, there is some value to speaking about power as if the whole grid concept didn't exist.
The factory will be 30 miles from one of the largest hydroelectric power plants on the planet. Unfortunately, it's more "economically advantageous" to transport that power to the New York City area and backfill Western New York with local power. Most of the local power comes from the Huntley Generating Station, which is a gas turbine plant that has been converted to coal. To add to the CO2 concerns, the way to use coal in a gas turbine plant is to crush the coal up so fine that it can be injected into the turbines using nozzles that were designed for methane. That makes Huntley one of the dirtiest places on earth.
As for nuclear, it will be more than 100 miles from the nearest nuclear power plant and that's only a small 600MW plant - the smallest in New York.
So, the biggest solar panel factory in the world is almost certain to be powered entirely by coal.
They didn't have enough cash. The reason they are building the plant in Buffalo is because New York State as paying for most of the up front capital. Before Musk, they had to find creative ways to grow the company and were likely to get trampled in the market by a competitor with the money to make market moves that Silevo couldn't afford to do. With Musk behind them, they can grow at whatever pace they can convince Musk they can be profitable at.
Slashdot Mirror
Some of that is intentional. For example, they make using a debit card as a credit card difficult because it saves them money. Walmart is the only store I know that labels the button to do so. Sometimes I ask how to do it just to give back a little of the frustration.
It's much more Web 2.0 to create a user interface that's minimal to the point of being cryptic, and to call users that can't figure it out idiots. It also helps to have a complete lack of standards.
There's a lot of room for improvement in programming languages. New features aren't just novelty. The database/language impedance mismatch is still pretty big, language feature to support multithreading are still weak, strongly typed languages still need to handle "dynamic-ness" better. Microsoft has done a great job of introducing new features that people actually want while still maintaining backwards compatibility. Oracle is being way too conservative here and it does matter to their customers - even the big ones.
I spent a lot of time recently working at a fortune 20 company. Java was the official programming language of the company, but the Enterprise Architecture group was starting to lean closer to .Net when I left.
For a language which forced Microsoft to up it's game with C#
Java has been playing catch up with C# for almost ten years. Attributes, generics, and lambdas were all added to Java long after they were added to C#. Also, Microsoft made them part of the runtime, while Java only made them part of the compiler (for the most part), so the features work a lot better in C#.
The point of this article is that Oracle has been slowing down the pace of innovation to an even slower pace than Sun was at, and Sun had already lost a five year head start to Microsoft very quickly.
"runtime and a language with a huge install base" describes a future where Java just coasts. By contrast, Python, Ruby, and .Net are all runtimes and languages (several languages in the case of .Net) with a huge install base that are actively introducing new frameworks, development tools, and feature on a regular basis. I'm calling an interpreter a runtime for the purposes of this conversation.
The number of possible valid credit card numbers is so small that any hashing solution can be brute forced very quickly, even if each record has its own salt. The only protection would be to make the algorithm secret, but then you've just reduced your system to security by obscurity and as soon as someone figures out the algorithm, you're toast.
I wouldn't recommend Office Automation on a server if there is any alternative. For beginners, there's too many gotchas and for advanced users, there's plenty of alternatives that will do what you want without too much difficulty. Office with .Net is especially problematic because the COM components run as out-of-process servers and due to .Net's garbage collection and COM interoperability, they are difficult to get to shut down properly.
In the payment card industry, this is called a token, not a hash. The difference is that a hash can be algorithmically generated from the source material, while a token cannot. Because there is no forward link outside the entity that generated the token to go from card to token, the tokens can be different at each merchant, making a loss of token much less of a problem than a loss of hashes would be. It's also 100% infeasible to break the token generating algorithm since there isn't one. In my experience, tokens are simply generated sequentially (skipping those that don't pass Luhn check). Another beauty of tokens is that they can pass validity checks for credit card numbers, so they can be handed to third-party software and treated just like card numbers, but without the risk of breach.
They implemented it the way they did so they can sell it as a drop-in solution that requires no coding changes. Unfortunately, a security technologies don't matter as much as processes do, so this product, like all other silver-bullet products, will never be all that good.
You mean regular DBAs like the next Edward Snowden? Inside threats are important and are one of the reasons this feature exists. LitchField did what he does best; he showed that the product doesn't quite live up to the marketing material.
How would a hashed credit card number ever be useful? You would have a really hard time sending a request for payment to a payment processor if you did.
They didn't say that. They said that the 40% "dwarfs the number of watchlisted people suspected of ties to al Qaeda, Hamas, and Hezbollah combined". That means that the second list is only a small portion of the remaining 60%. It also means that most of the 60% aren't suspected of having ties to the three groups - and therefore also are probably false positives. Note that they said "suspected", most of the 60% aren't even suspected of having ties to the big three.
It's different because the agencies with security as their middle name don't have a backdoor for this.
That's why I was careful to say "end-to-end encryption" instead of "https". If you aren't using the public CA infrastructure, your data may be private.
Is this article suggesting that new communication paradigms are a bad idea because the security gear optimized for the old paradigm won't work? Should we wait for the security industry to invent multipath TCP? BTW, this is the same security gear that can already be thwarted by end-to-end encryption. How is this any different?
Believe me, this install will never be PCI complaint. Either they will choose a solution that doesn't store cardholder data, or will outsource the credit card processing to someone else. It isn't cost effective to have a PCI compliant installation this small. So, this issue can be ignored when discussing "should a server like this have a firewall?".
Yes, it's legal. But, Southwest's Contract of Carriage lists 13 reasons that boarding can be denied. "We disagree with you" isn't on the list. So, they violated their own contract and they owe the passenger between 200 and 400 percent of the fare, depending on how late he gets to his destination.
Tweet after you land and your family and friends read it. Tweet before you take off and it gets on the front page of Slashdot. I'd say he played it exactly the right way to both get to where he was going and to make as much bad Southwest publicity as possible.
KMart was run into bankruptcy 13 years ago by it's CEO and COO. I don't mean they happened to be there while something bad happened, I mean that business strategy that was chosen directly caused the bankruptcy. The COO was the one making most of the calls and his previous two jobs got rid of him when they went bankrupt (Hechinger, Big V Supermarkets). Yes, he bankrupted three companies in a row. He's still an executive. Also, when he left KMart, he wasn't really fired - he "left voluntarily" and on the way out he was given a 3 million dollar loan and a document that said he would never have to pay back that loan. They did that because they weren't allowed to give him a bonus due the whole Chapter 11 thing and they felt so bad that he was going to be out of a job and needing to live on his meager eight figure investment portfolio.
Isn't this just another form of the "illegal to be black" line of thinking? Just because you have a certain skin color or live in a certain neighborhood doesn't automatically mean you should be treated like a criminal. Sure it's expedient for cops to make these generalizations, but it's wrong.
I would like to have seen the original example as "The city government that maintains the roads and traffic control devices would be liable for allowing the suspect to get away fast enough to evade capture".
Visual Basic went to .Net five versions ago. It was acceptable to take VB to mean classic VB in 2003, but in 2014, you have to say so if you mean the old stuff. The VB6 development environment doesn't even run on any supported operating system. VBA is still around, but it's always been incorrect to refer to VBA as VB.
I think it's interesting that you know Visual Basic, but want to get into C#. My first question would be "Why?". Both run on the same framework and both are equally capable. All you're doing is learning new syntax to do things you already know how to do. After that question is the comment "You pretty much already know C#". Sure, it's a different language from VB, but that's the easy part. It uses the same tools and libraries, so you know 95% of it already.
You are absolutely 100 percent technically correct. But whoever gets their power at hydro rates is the consumer of hydro power. If Robert Moses was shut down, the customers paying the lower rate would either have to pay more or stop receiving power (or the person who wrote the contract would lose money). The people paying coal rates would be easy to serve by bringing power from coal plant at other points on the grid. So, for all intents and purposes, they are getting the power from Robert Moses.
We could extend this process to things like carbon credits and any future non-renewable tax. The providers would only be able to sell a certain quantity of "penalty-exempt" power. That would drive the market for that power, even thought the customer may not receive exactly the electron they paid for. So, there is some value to speaking about power as if the whole grid concept didn't exist.
The factory will be 30 miles from one of the largest hydroelectric power plants on the planet. Unfortunately, it's more "economically advantageous" to transport that power to the New York City area and backfill Western New York with local power. Most of the local power comes from the Huntley Generating Station, which is a gas turbine plant that has been converted to coal. To add to the CO2 concerns, the way to use coal in a gas turbine plant is to crush the coal up so fine that it can be injected into the turbines using nozzles that were designed for methane. That makes Huntley one of the dirtiest places on earth.
As for nuclear, it will be more than 100 miles from the nearest nuclear power plant and that's only a small 600MW plant - the smallest in New York.
So, the biggest solar panel factory in the world is almost certain to be powered entirely by coal.
They didn't have enough cash. The reason they are building the plant in Buffalo is because New York State as paying for most of the up front capital. Before Musk, they had to find creative ways to grow the company and were likely to get trampled in the market by a competitor with the money to make market moves that Silevo couldn't afford to do. With Musk behind them, they can grow at whatever pace they can convince Musk they can be profitable at.