I own a 1980 Triumph TR-8. No ABS, anti-lock, traction control, air bags, EFI (it's carbureted), bluetooth, or GPS; therefore, no computers. The most modern thing in it is the stereo, a Clarion from 1993. It's even got manual door locks and windows. Analog clock. Mechanical speedo, tach and odometer.
I'd like to see them try to apply DRM to it.
Sometimes, being a partial Luddite can be a good thing.
For states that set up their own exchanges, there are generally offices available as well as phone lines people can call. Many of the states that opted out are also trying their damnedest to block any perceived successes for the ACA, and have taken steps to hinder their establishment. How much help someone can expect in signing up depends entirely on what state you're talking about.
Can't wait for The Stig to take it round the track. Some say his home computer is a Commodore Amiga, and he still believes 640K is more than enough RAM for anyone.
There's no sure way to protect the data, but this comes close:
1. Unplug the server/storage array/whatever 2. Put it in a safe. Lock the safe, lose the combo. 3. Dig a large hole. 4. Insert safe into hole. 5. Fill hole with concrete.
Of course, even this plan has its flaws: What if the safe is discovered? Your only hope is that it's discovered by a Redditor; it will never be opened then.
I already have something like this. I input basic food components (including powders and oil, as needed) in a ordered fashion (sometimes layer by layer), and after a short time, I extract a customized, nutritionally-appropriate meal.
Microsoft confirmed the remote code-execution vulnerability on Friday night. Versions 6, 7, 9, and 10 of the browser are immune to these attacks, so anyone who can upgrade to one of the latest two versions should do so immediately or switch to a different browser. For anyone who absolutely can not move away from IE 8, company researchers recommend the following precautions:
Proper procedures for any IT or security dismissal (or really, for anyone with access to sensitive/proprietary information) is escorting them from the building, disabling their access while they are being told that they're terminated. Any external access they have is revoked by the time the get to the front door; any shared accounts they know (like root, su or domain admin) have their external access suspended until the passwords can be changed. Collect their IDs, corporate cell phone, USB devices, etc. before they leave the premises; they can make an appointment to come back and get them after they've been inspected for any proprietary information. Don't let them go back to their desks and get anything - either send someone to get it for them, or tell them they can get it when they return for the other stuff.
This needs to be part of the process for ANY termination, even if the employee has been a model of behavior and is taking their change of status phenomenally well. People in stressful situations can behave erratically and unpredictably, and the organization must protect themselves against an unexpected reprisal. I've seen people throw away extremely generous separation packages in favor of revenge via venting on Facebook or sending abusive/threatening emails to the CEO. And I wondered what the hell was going through their heads, right up until I got downsized myself in the middle of the recession. I chose to accept, regroup and move on, but I now have a much better understanding of the stress something like that brings to bear.
You were one of the first Hollywood writers with an online presence, hanging out in newsgroups during production of Babylon 5. My memories of that were tidbits and insights from you, along with frequent "no story submissions" reminders and threats of your departure if the story ideas didn't stop. How do you remember that experience? Was it worth the hassle? And do you view the seeming explosion of writers, directors, producers and actors on social media as a positive or negative for the industry overall?
Udacity and Coursera both offer free online college-level courses in programming. Udacity's focus is primarily on Python (at least in the courses I've taken), but it looks like Coursera's offerings include C++. Any of these should give him a good start in object-oriented programming.
You have to start with the position that no OS, network, or configuration is ever going to be 100% secure. If the system is accessible by someone via some means, it has at least one vulnerability.
This is why blanket questions as asked in the original posts are worse than useless. Asking is certain OSes have vulnerabilities (they do) is a waste of time. Looking for bogey-men like government backdoors or vendor/service providers is equally useless: either they exist and you can't do anything about them, or they don't and you're worrying about nothing.
But the biggest problem with blanket questions is that they lead to one-size-fits-all thinking. And with designing a secure environment, there is no one size that fits all. What works perfectly is one environment is a huge overcompensation in another, and woefully inadequate in a third. You have to look at your specific environment, including business processes (involving humans, not just electrons), resources, physical environment, everything. If you're considering setting up security, don't think in terms of "secure computing environment", think "secure environment." Limiting your scope to the computing environment only introduces blind spots (vulnerabilities).
I call this reasoned paranoia for two reasons: it serves a distinct purpose, and it stops short of tin-hat thinking. Your approach needs to keep what you can do as the focus. You can't close government backdoors, if they even exist. You can't stop hackers in Pyongyang from probing your firewall. You can't close (or even know about) every vulnerability that currently exists in your environment. But you can understand that they are there, take reasonable steps to close or manage the ones you know about, and have plans in place to respond when new ones are discovered or exploited.
As someone currently enrolled at Udacity, I can confirm that I'm only taking a couple courses at the moment. That's the advantage - I can learn at my own pace, in a manner that suits both my schedule and style of learning, and get the most possible benefit out of the classes. I'm not saying that I would outperform a Stanford student; hell, I wouldn't even pass the admissions test. And yet, I'm currently participating in Stanford-level classes in computer science, physics and statistics. For free.
IMHO, that's a pretty compelling argument for the value of this effort.
Just what we need: a one-stop shop for 0-day exploit code. Way to improve security, guys! Right on! Stick it to The Man! And by that, I mean the man (or woman) in the next cubical, or next door, or down the street, or....
I am all for responsible disclosure of vulnerabilities - secrecy does not equal security, and "let's not talk about it and hope nobody notices" is never an appropriate response to vulnerabilities. But responsible disclosure includes working with the vendor, giving them the full data and an opportunity to correct prior to full public disclosure.
If MS is giving researchers the cold shoulder or worse in response to vulnerabilities that are responsibly disclosed to them, that's shame on Microsoft. But to my view, jumping to public disclosure is not the appropriate response.
From the Colorado River -- Nevada has been trying to get a greater allocation for a long time and this would get the Feds in on their side. Or, of course, there's all the sewage from Las Vegas. Whenever the wind is headed out of state they can just use that for coolant.
Read the article - they're talking Northern Nevada. That's about 450 miles from Las Vegas. The only time Reno is near Vegas is on CSI. And that's no credible source; half of the cast can't even say "Nevada" correctly.
If you accidentally tick off The Big One and Southern California falls into the ocean, all you'll have left are those crazy Northern California people, and we'll -so- become a Red State.
Ever been to Berkeley? San Francisco? California only becomes a Red state if Orange County and San Diego are all that's left.
Or did you mean Red as in Commie? That would be a real possibility.
Slashdot Mirror
I own a 1980 Triumph TR-8. No ABS, anti-lock, traction control, air bags, EFI (it's carbureted), bluetooth, or GPS; therefore, no computers. The most modern thing in it is the stereo, a Clarion from 1993. It's even got manual door locks and windows. Analog clock. Mechanical speedo, tach and odometer.
I'd like to see them try to apply DRM to it.
Sometimes, being a partial Luddite can be a good thing.
Oh, yeah, it's a real kick to drive....
For states that set up their own exchanges, there are generally offices available as well as phone lines people can call. Many of the states that opted out are also trying their damnedest to block any perceived successes for the ACA, and have taken steps to hinder their establishment. How much help someone can expect in signing up depends entirely on what state you're talking about.
Some deep watering and maybe a little Miracle Gro, I bet we can get those suckers down to the Permian.
Can't wait for The Stig to take it round the track. Some say his home computer is a Commodore Amiga, and he still believes 640K is more than enough RAM for anyone.
There's no sure way to protect the data, but this comes close:
1. Unplug the server/storage array/whatever
2. Put it in a safe. Lock the safe, lose the combo.
3. Dig a large hole.
4. Insert safe into hole.
5. Fill hole with concrete.
Of course, even this plan has its flaws: What if the safe is discovered? Your only hope is that it's discovered by a Redditor; it will never be opened then.
I would use this as the music under the title: http://www.youtube.com/watch?v=rrYhWVMqf-4
I'd much rather pay royalties to Stravinsky's estate than to the publishing company.
TIL the entire movie will be shot from 3 feet above and 6 feet behind the main character.
Alliterative aspects augment awesome article attributes.
I already have something like this. I input basic food components (including powders and oil, as needed) in a ordered fashion (sometimes layer by layer), and after a short time, I extract a customized, nutritionally-appropriate meal.
It's called an "oven".
From the article:
Microsoft confirmed the remote code-execution vulnerability on Friday night. Versions 6, 7, 9, and 10 of the browser are immune to these attacks, so anyone who can upgrade to one of the latest two versions should do so immediately or switch to a different browser. For anyone who absolutely can not move away from IE 8, company researchers recommend the following precautions:
Helpfully, Microsoft has pulled that advisory. Going to http://technet.microsoft.com/en-us/security/advisory/2847140 gets you a 404 error message now.
Thanks, Microsoft!
Proper procedures for any IT or security dismissal (or really, for anyone with access to sensitive/proprietary information) is escorting them from the building, disabling their access while they are being told that they're terminated. Any external access they have is revoked by the time the get to the front door; any shared accounts they know (like root, su or domain admin) have their external access suspended until the passwords can be changed. Collect their IDs, corporate cell phone, USB devices, etc. before they leave the premises; they can make an appointment to come back and get them after they've been inspected for any proprietary information. Don't let them go back to their desks and get anything - either send someone to get it for them, or tell them they can get it when they return for the other stuff.
This needs to be part of the process for ANY termination, even if the employee has been a model of behavior and is taking their change of status phenomenally well. People in stressful situations can behave erratically and unpredictably, and the organization must protect themselves against an unexpected reprisal. I've seen people throw away extremely generous separation packages in favor of revenge via venting on Facebook or sending abusive/threatening emails to the CEO. And I wondered what the hell was going through their heads, right up until I got downsized myself in the middle of the recession. I chose to accept, regroup and move on, but I now have a much better understanding of the stress something like that brings to bear.
Green rock, from outer space, found in northern Africa?
Miss Tessmacher! Cancel the tickets to Addis Ababa! We're going to Morroco!
You were one of the first Hollywood writers with an online presence, hanging out in newsgroups during production of Babylon 5. My memories of that were tidbits and insights from you, along with frequent "no story submissions" reminders and threats of your departure if the story ideas didn't stop. How do you remember that experience? Was it worth the hassle? And do you view the seeming explosion of writers, directors, producers and actors on social media as a positive or negative for the industry overall?
Amazingly, the "twighlight" of data centers coincides with the twilight of spell-checking.
Popcorn? You're munching popcorn?
Hmph. Everyone knows corn nuts are the best snack for well-reasoned and rational comment watching!
Udacity and Coursera both offer free online college-level courses in programming. Udacity's focus is primarily on Python (at least in the courses I've taken), but it looks like Coursera's offerings include C++. Any of these should give him a good start in object-oriented programming.
Nothing is truly secure, it's simply in a state where the vulnerabilities haven't been discovered yet.
You have to start with the position that no OS, network, or configuration is ever going to be 100% secure. If the system is accessible by someone via some means, it has at least one vulnerability.
This is why blanket questions as asked in the original posts are worse than useless. Asking is certain OSes have vulnerabilities (they do) is a waste of time. Looking for bogey-men like government backdoors or vendor/service providers is equally useless: either they exist and you can't do anything about them, or they don't and you're worrying about nothing.
But the biggest problem with blanket questions is that they lead to one-size-fits-all thinking. And with designing a secure environment, there is no one size that fits all. What works perfectly is one environment is a huge overcompensation in another, and woefully inadequate in a third. You have to look at your specific environment, including business processes (involving humans, not just electrons), resources, physical environment, everything. If you're considering setting up security, don't think in terms of "secure computing environment", think "secure environment." Limiting your scope to the computing environment only introduces blind spots (vulnerabilities).
I call this reasoned paranoia for two reasons: it serves a distinct purpose, and it stops short of tin-hat thinking. Your approach needs to keep what you can do as the focus. You can't close government backdoors, if they even exist. You can't stop hackers in Pyongyang from probing your firewall. You can't close (or even know about) every vulnerability that currently exists in your environment. But you can understand that they are there, take reasonable steps to close or manage the ones you know about, and have plans in place to respond when new ones are discovered or exploited.
Aw, that's not so hard. I used to bulls-eye womprats in my T-38 back home, and they're not much bigger than 1.5 meters.
As someone currently enrolled at Udacity, I can confirm that I'm only taking a couple courses at the moment. That's the advantage - I can learn at my own pace, in a manner that suits both my schedule and style of learning, and get the most possible benefit out of the classes. I'm not saying that I would outperform a Stanford student; hell, I wouldn't even pass the admissions test. And yet, I'm currently participating in Stanford-level classes in computer science, physics and statistics. For free.
IMHO, that's a pretty compelling argument for the value of this effort.
Let's see, I've got $0.73 in my pocket. Think they can make change?
... is the AUTOMOBILE!
Duh duh duuunnnnnnnn!
Just what we need: a one-stop shop for 0-day exploit code. Way to improve security, guys! Right on! Stick it to The Man! And by that, I mean the man (or woman) in the next cubical, or next door, or down the street, or....
I am all for responsible disclosure of vulnerabilities - secrecy does not equal security, and "let's not talk about it and hope nobody notices" is never an appropriate response to vulnerabilities. But responsible disclosure includes working with the vendor, giving them the full data and an opportunity to correct prior to full public disclosure.
If MS is giving researchers the cold shoulder or worse in response to vulnerabilities that are responsibly disclosed to them, that's shame on Microsoft. But to my view, jumping to public disclosure is not the appropriate response.
From the Colorado River -- Nevada has been trying to get a greater allocation for a long time and this would get the Feds in on their side. Or, of course, there's all the sewage from Las Vegas. Whenever the wind is headed out of state they can just use that for coolant.
Read the article - they're talking Northern Nevada. That's about 450 miles from Las Vegas. The only time Reno is near Vegas is on CSI. And that's no credible source; half of the cast can't even say "Nevada" correctly.
If you accidentally tick off The Big One and Southern California falls into the ocean, all you'll have left are those crazy Northern California people, and we'll -so- become a Red State.
Ever been to Berkeley? San Francisco? California only becomes a Red state if Orange County and San Diego are all that's left.
Or did you mean Red as in Commie? That would be a real possibility.