So you are indeed saying that warnings are more secure than preventing access? That's like saying a security guard that tells you people might be tresspassing is doing a better job than a security guard who stopped people from tresspassing. That's your argument.
To be you think a warning about suspect parts after they've accessed the system is more secure than preventing suspect parts from accessing the systems? Am I understanding that correctly? You could say the latter may overkill and more restrictive but I wouldn't argue it's less secure.
I never claimed that Linux is useless to Android. That's a straw man argument. What I claimed is simply that Android isn't Linux. Android is built on top of Linux; however, the default UI for Linux is bash. That point seems lost on the OP.
So how does invoking Android help a consumer when dealing with an issue involving laptops and desktops? You could mention Chromebooks or PCs with Windows 10 but I doubt you'd get a lot of support of Windows 10 here on/.
Er what? You can argue with this move has other effects but you can't argue that it doesn't enhance security. However if we go with your argument that everyone's computer could be comprised, what is the course of action? Nothing?
Only if you didn't understand his comment in that Linux absolutely does little for the UI. Linux is the kernel. You can have a great UI or a terrible UI on top of Linux.
Because at that point the user might already be comprised and the rogue hardware may prevent any such warning. Then there would be outcry from some people about Apple not doing more to protect them. The repair facility may not have any ill intention; they just used a cheaper part.
Did you know that many Dells are made in China using chips made in China? Did you know many Lenovos are made in China using chips made in China? And the list goes on and on.
The real financial problems were caused by the LBO in 2005. KKR and Bain Capital (Mitt Romney's former company) bought out Toys R Us for $6.6B and assumed $1B debt. The way the buyout was structured Toys R Us had to acquire $6.3B in debt. For those that don't know, most LBOs are structured so that the company being bought has to take on the debt. It is perfectly legal.
Many people would assume that the company merely lost out to Amazon but that's not the whole story. With $6.3B in debt, the company was severely hampered in what it could do to compete with Amazon. Improving server infrastructure, buying new stores, practically anything was limited by the fact that they couldn't borrow any more money. And a large portion of the revenue that was earned had to pay off the debt so it couldn't spend any real capital either.
Wally: What's this? (Holds up a piece of paper)
PHB: It's the new non-compete agreement everyone has to sign. By signing it, you agree not to do any work for a competitor for a year.
Wally: (signs it) Here you go.
Wally: (as he leaves PHB's office). I haven't done any work for this company in the last 5 years.
I was once hired to replace a guy making $100K+ a year who quit because they were increasing his workload and he felt it was too much. Overwork happens in IT but when I was analyzing what he actually did, I don't see how he got away with it. He spent half the day receving previous day's orders from the database in one format, putting it into Excel, then converting into another format that the order system could handle. The rest of the day, he did nothing. Yet he complained about "more" work. For the first month when I did it manually it might take 2 hours tops with checking to make sure the orders were right.
The second month, I automated all of it with a stored procedure. It ran every morning and took five minutes. My bosses at first thought I was some sort of genius for automating a task until I showed them what I did. My coworkers (and his former coworkers) were more shocked that he worked so long at the company and did so little.
Cost is a huge factor. Not just to cost to print the manual but the cost to ship the manual as well. If a manual is 1 kg or 2.2 lbs, what's the total cost to ship the manuals from the printing plant to the assembly plant? If the product run is 100,000 units, that's 100,000 kg to ship. Then the additional weight is added to the shipping weight of the final product which is an additional cost.
In your hypothetical, you've actually changed the lock by damaging it. I can't see how you can argue you didn't tamper with it. If your phone is locked with a passcode or a biometric sensor, it's still locked regardless.
Deliberately locking it in this way irretrievably wipes one of the keys used to unlock the device's master encryption key. A new key for use by FaceID won't be generated until and unless the phone is unlocked via a passcode.
Do you have proof of this claim? Also if your device does not have Face ID enabled or have it, what then?"
There are gads of ways they are different; however, as coders we neither have the ability, permission, or control to make sure that they are identitical in every single way. In some cases these are unavoidable. The production environment is a 6 cpu server located in CA for example. The Dev and Test servers are 2 CPU servers located locally. But here's the thing: as coders we made sure that we developed on the as close to Production as we could. We didn't think that a db driver was enough to cause a difference. In this case we had to patch the code immediately and the sysadmins had to test the effect of deploying the new driver to Production. That second part took 6 weeks.
Yes and no. Yes it's in technology but the technology itself leads to more advancements in science. From the press release:
Advanced precision instruments are opening up unexplored areas of research and a multitude of industrial and medical applications. . . Strickland and Mourouâ(TM)s newly invented technique, called chirped pulse amplification, CPA, soon became standard for subsequent high-intensity lasers . . . The innumerable areas of application have not yet been completely explored.
No if your deliberately passcode lock your, you haven't tampered with evidence as the evidence still exists as it did before you touched the device. The police can't access the device which is the same position they were before they handed it to you.
And how in the world would this have helped us? Like I said the only difference was the db driver on Production was different. Otherwise everything else was the same. The same applications, same toolset, the same versions, same databases, etc. Testing didn't find the problem because it didn't exist on Test or Dev.
Sometimes it's a very slight difference between environments that causes problems. We rolled out some code to production that had been fully tested in Dev and Test environments. Things started to break due to SQL errors. Ran the SQL directly on the production database server but it ran fine. Somehow the SQL was getting different results running through the production server than it was on the production database server directly.
After some investigation the only difference between the production server and other environments was the server used a slightly older database driver. It was a minor version difference. How this caused errors was that in the older db driver all math operations had to be explicit data casts despite what documentation said but the newer driver followed the database documentation. So Integer A / Integer B should be implicitly cast as Integer according to the documentation. However the older driver would cast that as Float for some unknown reason and that would cause errors.
But this would only happen using the db driver on Production. Testing the SQL directly on Production DB wouldn't have found it. Testing the code and SQL on Dev and Test servers wouldn't have found the bug. The patch notes for the db driver didn't mention the change.
Slashdot Mirror
So you are indeed saying that warnings are more secure than preventing access? That's like saying a security guard that tells you people might be tresspassing is doing a better job than a security guard who stopped people from tresspassing. That's your argument.
To be you think a warning about suspect parts after they've accessed the system is more secure than preventing suspect parts from accessing the systems? Am I understanding that correctly? You could say the latter may overkill and more restrictive but I wouldn't argue it's less secure.
I never claimed that Linux is useless to Android. That's a straw man argument. What I claimed is simply that Android isn't Linux. Android is built on top of Linux; however, the default UI for Linux is bash. That point seems lost on the OP.
So how does invoking Android help a consumer when dealing with an issue involving laptops and desktops? You could mention Chromebooks or PCs with Windows 10 but I doubt you'd get a lot of support of Windows 10 here on /.
Er what? You can argue with this move has other effects but you can't argue that it doesn't enhance security. However if we go with your argument that everyone's computer could be comprised, what is the course of action? Nothing?
Only if you didn't understand his comment in that Linux absolutely does little for the UI. Linux is the kernel. You can have a great UI or a terrible UI on top of Linux.
Because at that point the user might already be comprised and the rogue hardware may prevent any such warning. Then there would be outcry from some people about Apple not doing more to protect them. The repair facility may not have any ill intention; they just used a cheaper part.
And how effective would an alert be once suspect parts are already accessing the system?
Did you know that many Dells are made in China using chips made in China? Did you know many Lenovos are made in China using chips made in China? And the list goes on and on.
Except that's not the whole story. Toys R Us was under massive debt from a LBO.
The real financial problems were caused by the LBO in 2005. KKR and Bain Capital (Mitt Romney's former company) bought out Toys R Us for $6.6B and assumed $1B debt. The way the buyout was structured Toys R Us had to acquire $6.3B in debt. For those that don't know, most LBOs are structured so that the company being bought has to take on the debt. It is perfectly legal.
Many people would assume that the company merely lost out to Amazon but that's not the whole story. With $6.3B in debt, the company was severely hampered in what it could do to compete with Amazon. Improving server infrastructure, buying new stores, practically anything was limited by the fact that they couldn't borrow any more money. And a large portion of the revenue that was earned had to pay off the debt so it couldn't spend any real capital either.
They gave me more tasks and a raise when it came time for reviews.
Wally: What's this? (Holds up a piece of paper)
PHB: It's the new non-compete agreement everyone has to sign. By signing it, you agree not to do any work for a competitor for a year.
Wally: (signs it) Here you go.
Wally: (as he leaves PHB's office). I haven't done any work for this company in the last 5 years.
I was once hired to replace a guy making $100K+ a year who quit because they were increasing his workload and he felt it was too much. Overwork happens in IT but when I was analyzing what he actually did, I don't see how he got away with it. He spent half the day receving previous day's orders from the database in one format, putting it into Excel, then converting into another format that the order system could handle. The rest of the day, he did nothing. Yet he complained about "more" work. For the first month when I did it manually it might take 2 hours tops with checking to make sure the orders were right.
The second month, I automated all of it with a stored procedure. It ran every morning and took five minutes. My bosses at first thought I was some sort of genius for automating a task until I showed them what I did. My coworkers (and his former coworkers) were more shocked that he worked so long at the company and did so little.
1lb or 1 kg: It adds additional cost in shipped expenses alone to put a manual in a product.
Cost is a huge factor. Not just to cost to print the manual but the cost to ship the manual as well. If a manual is 1 kg or 2.2 lbs, what's the total cost to ship the manuals from the printing plant to the assembly plant? If the product run is 100,000 units, that's 100,000 kg to ship. Then the additional weight is added to the shipping weight of the final product which is an additional cost.
In your hypothetical, you've actually changed the lock by damaging it. I can't see how you can argue you didn't tamper with it. If your phone is locked with a passcode or a biometric sensor, it's still locked regardless.
Deliberately locking it in this way irretrievably wipes one of the keys used to unlock the device's master encryption key. A new key for use by FaceID won't be generated until and unless the phone is unlocked via a passcode.
Do you have proof of this claim? Also if your device does not have Face ID enabled or have it, what then?"
There are gads of ways they are different; however, as coders we neither have the ability, permission, or control to make sure that they are identitical in every single way. In some cases these are unavoidable. The production environment is a 6 cpu server located in CA for example. The Dev and Test servers are 2 CPU servers located locally. But here's the thing: as coders we made sure that we developed on the as close to Production as we could. We didn't think that a db driver was enough to cause a difference. In this case we had to patch the code immediately and the sysadmins had to test the effect of deploying the new driver to Production. That second part took 6 weeks.
Advanced precision instruments are opening up unexplored areas of research and a multitude of industrial and medical applications. . . Strickland and Mourouâ(TM)s newly invented technique, called chirped pulse amplification, CPA, soon became standard for subsequent high-intensity lasers . . . The innumerable areas of application have not yet been completely explored.
No if your deliberately passcode lock your, you haven't tampered with evidence as the evidence still exists as it did before you touched the device. The police can't access the device which is the same position they were before they handed it to you.
From what I remember, the SQL vendor didn't write the driver but neither did the application vendor. It was a 3rd party driver.
And how in the world would this have helped us? Like I said the only difference was the db driver on Production was different. Otherwise everything else was the same. The same applications, same toolset, the same versions, same databases, etc. Testing didn't find the problem because it didn't exist on Test or Dev.
Sometimes it's a very slight difference between environments that causes problems. We rolled out some code to production that had been fully tested in Dev and Test environments. Things started to break due to SQL errors. Ran the SQL directly on the production database server but it ran fine. Somehow the SQL was getting different results running through the production server than it was on the production database server directly.
After some investigation the only difference between the production server and other environments was the server used a slightly older database driver. It was a minor version difference. How this caused errors was that in the older db driver all math operations had to be explicit data casts despite what documentation said but the newer driver followed the database documentation. So Integer A / Integer B should be implicitly cast as Integer according to the documentation. However the older driver would cast that as Float for some unknown reason and that would cause errors.
But this would only happen using the db driver on Production. Testing the SQL directly on Production DB wouldn't have found it. Testing the code and SQL on Dev and Test servers wouldn't have found the bug. The patch notes for the db driver didn't mention the change.
Green Bay doesn't own "Titletown Tech". If they did that would be another discussion.