I thought the same as you; but have recently gotten back into running (real-world) and thought "Meh, increasing incline doesn't do anything." Then I tried it. Holy hell. The incline increase forces you to use different muscles - even though the motor is still powering the belt underneath, you utilize more of your calves on a sharper incline. Seems to mimic more of a hill than one would normally think as you have to adjust your balance to stay upright.
I would buy a car for 75k if it would run reliably for 500k miles. Now - this doesn't mean 0 service needed; however it would have to be minimal (1-2k a year at most.)
My current car is at 124k. It's not in bad shape - in fact, I could probably stand to pour another 1-2k in it this year to get it driving perfectly. But the seat (driver's side) is wearing (foam all compressed, leather is getting kinda fugly). Door seals don't quite seal out the wind like they used to; headliner in the back is peeling a little (nothing a little glue won't help...) etc. But I've not had a payment on it for 3 years now, and I don't want that to change unless it gets totaled.
Got an idea - get a 12v to usb adapter (cig lighter/power port - whatever you want to call it) for your vehicle. Covers both scenarios: a. camping. Someone has a vehicle around, and even if you don't start the car you can get a bunch of charges into the light. b. power goes out - again, there is a car somewhere. Anyhow; my main point here is this - in Ohio we had the power go out maybe 3 years ago - pretty bad wind storms. Most of the stores nearby were shut down due to lack of power, so getting batteries meant driving somewhere. Granted, had to go get food etc - but for the first few days, we just ate what we could in the pantry etc. Charging via USB I think is not the worst way to go; the other option is to use an inverter - again, off the car. I kept my fridge cool on day 1 using that. Of course, I also have some SLA batteries on charge for power outages too....
My driver for UPS used to be cool. Any packages needed delivered would always be after 5pm (usually 5:30 on the dot) therefore we were always home to get them. The last 2 packages required signatures and were attempted sometime during the day. Since my wife wasn't home this time around, I got the little "we missed you, no we can't leave it" slip. For the first package - a TV - I was cool; just took the trip down to pick it up. Takes 55 minutes to get it (total travel time + pickup) but I was geeked so it was worth it. The second? I looked on the slip that the driver left - stated would be back between 2-5pm and 5pm+ the next day. So I took 1/2 a day from work since I figured an hour of my time would be worth that and nope, I get home at 12:30pm and there's another slip. I called UPS and raised hell; the best they could tell me is that the times are approximate and they couldn't redeliver that day. I spent another 55 minutes getting the package. Not to mention that you can only pick the items up between 7:30 and 8:30pm; kind of limits your evening. This is why I will pay extra for Fed Ex in the future (heck, the receiving office is on the way home from work too!).
Keep in mind too that you're only seeing one end of the conversation. S/N ratio can be good for the downstream (AP --> Laptop/client radio) but crapola for the other direction (client --> AP) and you won't ever see it unless you're monitoring the AP side of the conversation.
Run into that one every now and again. User has good signal, but the laptop just isn't getting to the AP.
Sorry; didn't realize you actually were the author of the main question. Was just going off of the comment thread - you stated "Not knowing what the apps I wanted to use would actually use, the results were largely meaningless."
Let's face it - you weren't lazy, but you also didn't come to the table with expectations. Not knowing what applications you want to use would probably be akin to going to a car/truck dealership and not knowing what you'd like your new vehicle to be able to do for you. And at that point - you could walk off the lot with an SUV when a compact car would have done the trick.
I traded my 99/4a for a 10 band stereo equalizer that was in use until about 4 months ago (and still works) and a CD player that I replaced the laser on once around '92 and then it finally died in 2000.... I'd say I probably got more out of the CD player/equalizer than I would have the 99/4a, even though I have fond memories.
***f****f****f******f******f**f**f*f*******f******f*f**f******f******f******** We noticed an issue yesterday and wanted to alert you to it. As a precaution, we're also forcing you to change your master password.
We take a close look at our logs and try to explain every anomaly we see. Tuesday morning we saw a network traffic anomaly for a few minutes from one of our non-critical machines. These happen occasionally, and we typically identify them as an employee or an automated script.
In this case, we couldn't find that root cause. After delving into the anomaly we found a similar but smaller matching traffic anomaly from one of our databases in the opposite direction (more traffic was sent from the database compared to what was received on the server). Because we can't account for this anomaly either, we're going to be paranoid and assume the worst: that the data we stored in the database was somehow accessed. We know roughly the amount of data transfered and that it's big enough to have transfered people's email addresses, the server salt and their salted password hashes from the database. We also know that the amount of data taken isn't remotely enough to have pulled many users encrypted data blobs.
If you have a strong, non-dictionary based password or pass phrase, this shouldn't impact you - the potential threat here is brute forcing your master password using dictionary words, then going to LastPass with that password to get your data. Unfortunately not everyone picks a master password that's immune to brute forcing.
To counter that potential threat, we're going to force everyone to change their master passwords. Additionally, we're going to want an indication that you're you, by either ensuring that you're coming from an IP block you've used before or by validating your email address. The reason is that if an attacker had your master password through a brute force method, LastPass still wouldn't give access to this theoretical attacker because they wouldn't have access to your email account or your IP.
We realize this may be an overreaction and we apologize for the disruption this will cause, but we'd rather be paranoid and slightly inconvenience you than to be even more sorry later.
We're also taking this as an opportunity to roll out something we've been planning for a while: PBKDF2 using SHA-256 on the server with a 256-bit salt utilizing 100,000 rounds. We'll be rolling out a second implementation of it with the client too. In more basic terms, this further mitigates the risk if we ever see something suspicious like this in the future. As we continue to grow we'll continue to find ways to reduce how large a target we are.
For those of you who are curious: we don't have very much data indicating what potentially happened and what attack vector could have been used and are continuing to investigate it. We had our asterisk phone server more open to UDP than it needed to be which was an issue our auditing found but we couldn't find any indications on the box itself of tampering, the database didn't show any changes escalating anyone to premium or administrators, and none of the log files give us much to go on.
We don't have a lot that indicates an issue occurred but it's prudent to assume where there's smoke there could be fire. We're rebuilding the boxes in question and have shut down and moved services from them in the meantime. The source code running the website and plugins has been verified against our source code repositories, and we have further determined from offline snapshots and cryptographic hashes in the repository that there was no tampering with the repository itself.
Again, we apologize for the inconvenience caused and will continue to take every precaution in protecting user data.
I apologize, I should also state there are explicit rules inside to outside too. Businesses should not run their servers like a home network to where the server has unfettered access outbound - or to other network areas, if necessary. Also - deep packet inspection on the firewall can nail a lot of what could be seen as unexpected protocols running across common ports (someone attempting ftp/SMB over port 80 for instance.)
As someone who works in protecting a large environment, I would never allow a server to run "open" on the internet without restricting access to the machine via a firewall. Any exploit that works against the machine could give external users access to other ports - which with a firewall in place, wouldn't cause instant chaos. There are definitely other avenues that you could work against here - but by whitelisting only what's needed from outside to inside, you'll be an order of magnitude safer against attacks you may not be knowledgeable about.
Slashdot Mirror
I thought the same as you; but have recently gotten back into running (real-world) and thought "Meh, increasing incline doesn't do anything." Then I tried it. Holy hell. The incline increase forces you to use different muscles - even though the motor is still powering the belt underneath, you utilize more of your calves on a sharper incline. Seems to mimic more of a hill than one would normally think as you have to adjust your balance to stay upright.
This doesn't work as well as you'd think when you're on a motorcycle though.
I would buy a car for 75k if it would run reliably for 500k miles. Now - this doesn't mean 0 service needed; however it would have to be minimal (1-2k a year at most.)
My current car is at 124k. It's not in bad shape - in fact, I could probably stand to pour another 1-2k in it this year to get it driving perfectly. But the seat (driver's side) is wearing (foam all compressed, leather is getting kinda fugly). Door seals don't quite seal out the wind like they used to; headliner in the back is peeling a little (nothing a little glue won't help...) etc. But I've not had a payment on it for 3 years now, and I don't want that to change unless it gets totaled.
Well, I personally have never had trouble with epileptics.
Damn kids, get off my lawn.
Java....
Remember Coke vs new Coke back in the day? Same thing. Enough users complain, "classic Netflix" will return.
Got an idea - get a 12v to usb adapter (cig lighter/power port - whatever you want to call it) for your vehicle. Covers both scenarios:
a. camping. Someone has a vehicle around, and even if you don't start the car you can get a bunch of charges into the light.
b. power goes out - again, there is a car somewhere.
Anyhow; my main point here is this - in Ohio we had the power go out maybe 3 years ago - pretty bad wind storms. Most of the stores nearby were shut down due to lack of power, so getting batteries meant driving somewhere. Granted, had to go get food etc - but for the first few days, we just ate what we could in the pantry etc. Charging via USB I think is not the worst way to go; the other option is to use an inverter - again, off the car. I kept my fridge cool on day 1 using that. Of course, I also have some SLA batteries on charge for power outages too....
My driver for UPS used to be cool. Any packages needed delivered would always be after 5pm (usually 5:30 on the dot) therefore we were always home to get them. The last 2 packages required signatures and were attempted sometime during the day. Since my wife wasn't home this time around, I got the little "we missed you, no we can't leave it" slip. For the first package - a TV - I was cool; just took the trip down to pick it up. Takes 55 minutes to get it (total travel time + pickup) but I was geeked so it was worth it. The second? I looked on the slip that the driver left - stated would be back between 2-5pm and 5pm+ the next day. So I took 1/2 a day from work since I figured an hour of my time would be worth that and nope, I get home at 12:30pm and there's another slip. I called UPS and raised hell; the best they could tell me is that the times are approximate and they couldn't redeliver that day. I spent another 55 minutes getting the package. Not to mention that you can only pick the items up between 7:30 and 8:30pm; kind of limits your evening. This is why I will pay extra for Fed Ex in the future (heck, the receiving office is on the way home from work too!).
Keep in mind too that you're only seeing one end of the conversation. S/N ratio can be good for the downstream (AP --> Laptop/client radio) but crapola for the other direction (client --> AP) and you won't ever see it unless you're monitoring the AP side of the conversation.
Run into that one every now and again. User has good signal, but the laptop just isn't getting to the AP.
Sorry; didn't realize you actually were the author of the main question. Was just going off of the comment thread - you stated "Not knowing what the apps I wanted to use would actually use, the results were largely meaningless."
Look at my horse
my horse is amazing
give it a lick
Mmm it tastes just like raisins
Let's face it - you weren't lazy, but you also didn't come to the table with expectations. Not knowing what applications you want to use would probably be akin to going to a car/truck dealership and not knowing what you'd like your new vehicle to be able to do for you. And at that point - you could walk off the lot with an SUV when a compact car would have done the trick.
You'll be alright as long as Phil Collins isn't playing in the background.
shut up woman, get on my horse
Tools and Utilities sounds like a folder for the male gangbangs... just saying.
I traded my 99/4a for a 10 band stereo equalizer that was in use until about 4 months ago (and still works) and a CD player that I replaced the laser on once around '92 and then it finally died in 2000.... I'd say I probably got more out of the CD player/equalizer than I would have the 99/4a, even though I have fond memories.
I SAID RST
lol
That depends. What's it hooked up to?
That's probably the unsubsidized cost of the Xperia. If you think about it, the PS3 is subsidized - via game purchases.
I like to separate content by asterisks. Slashdot complained, so I put in random 'f's to circumvent the filter...
Note: This is taken from http://blog.lastpass.com/2011/05/lastpass-security-notification.html
***f****f****f******f******f**f**f*f*******f******f*f**f******f******f********
We noticed an issue yesterday and wanted to alert you to it. As a precaution, we're also forcing you to change your master password.
We take a close look at our logs and try to explain every anomaly we see. Tuesday morning we saw a network traffic anomaly for a few minutes from one of our non-critical machines. These happen occasionally, and we typically identify them as an employee or an automated script.
In this case, we couldn't find that root cause. After delving into the anomaly we found a similar but smaller matching traffic anomaly from one of our databases in the opposite direction (more traffic was sent from the database compared to what was received on the server). Because we can't account for this anomaly either, we're going to be paranoid and assume the worst: that the data we stored in the database was somehow accessed. We know roughly the amount of data transfered and that it's big enough to have transfered people's email addresses, the server salt and their salted password hashes from the database. We also know that the amount of data taken isn't remotely enough to have pulled many users encrypted data blobs.
If you have a strong, non-dictionary based password or pass phrase, this shouldn't impact you - the potential threat here is brute forcing your master password using dictionary words, then going to LastPass with that password to get your data. Unfortunately not everyone picks a master password that's immune to brute forcing.
To counter that potential threat, we're going to force everyone to change their master passwords. Additionally, we're going to want an indication that you're you, by either ensuring that you're coming from an IP block you've used before or by validating your email address. The reason is that if an attacker had your master password through a brute force method, LastPass still wouldn't give access to this theoretical attacker because they wouldn't have access to your email account or your IP.
We realize this may be an overreaction and we apologize for the disruption this will cause, but we'd rather be paranoid and slightly inconvenience you than to be even more sorry later.
We're also taking this as an opportunity to roll out something we've been planning for a while: PBKDF2 using SHA-256 on the server with a 256-bit salt utilizing 100,000 rounds. We'll be rolling out a second implementation of it with the client too. In more basic terms, this further mitigates the risk if we ever see something suspicious like this in the future. As we continue to grow we'll continue to find ways to reduce how large a target we are.
For those of you who are curious: we don't have very much data indicating what potentially happened and what attack vector could have been used and are continuing to investigate it. We had our asterisk phone server more open to UDP than it needed to be which was an issue our auditing found but we couldn't find any indications on the box itself of tampering, the database didn't show any changes escalating anyone to premium or administrators, and none of the log files give us much to go on.
We don't have a lot that indicates an issue occurred but it's prudent to assume where there's smoke there could be fire. We're rebuilding the boxes in question and have shut down and moved services from them in the meantime. The source code running the website and plugins has been verified against our source code repositories, and we have further determined from offline snapshots and cryptographic hashes in the repository that there was no tampering with the repository itself.
Again, we apologize for the inconvenience caused and will continue to take every precaution in protecting user data.
The LastPass Team.
UPDATE 1: We're overloaded handling support and
I apologize, I should also state there are explicit rules inside to outside too. Businesses should not run their servers like a home network to where the server has unfettered access outbound - or to other network areas, if necessary. Also - deep packet inspection on the firewall can nail a lot of what could be seen as unexpected protocols running across common ports (someone attempting ftp/SMB over port 80 for instance.)
As someone who works in protecting a large environment, I would never allow a server to run "open" on the internet without restricting access to the machine via a firewall. Any exploit that works against the machine could give external users access to other ports - which with a firewall in place, wouldn't cause instant chaos. There are definitely other avenues that you could work against here - but by whitelisting only what's needed from outside to inside, you'll be an order of magnitude safer against attacks you may not be knowledgeable about.
Doesn't matter; the process isn't running anymore and can't be found.