Aug. 4th, 2017
And it will...yes, it will, too. This whole "selling access to your own photos back to you for oh, just a mere $399" is simply their end game to recoup enough lost money in operating costs to fund severance packages for their already overwhelmed and beleaguered employees trapped as they are in a chaotic and disorganized workplace so they can lay everyone off and just shut down, already.
That's my wild guess - perhaps wishful thinking on my part, but hey, after the painful hours of work I endured to painstakingly replace images on my other blog so they could never ransom them again like they did the night I began that process (for some reason they stopped ransoming them not more than a few hours after I bitched about them doing so on the front page of that blog, but I kept replacing them by uploading dupes to Wordpress and relinking them in each post by hand, anyhow), I surely deserve to indulge in whatever flights of fancy I desire.
Oh, but how I digress...I specifically want Photobucket to go up in one big fat burst of orange flames because once they finally deleted the account I replaced the images on (and I have no idea when they deleted it because I haven't been online to check up on the MM side of my life in about a week) they began running ads on the error page that now stands in place of my account, like so - and of course it's an "error" page because they'll never admit their ransom plan has failed spectacularly and we're actually "deleting" our accounts in hordes.
I wanted to post this over a week ago (7-24, according to my computer when I screencapped the relevant messages) but life's got a way of getting in the way. I'll assume (though perhaps in error) that it's untriaged/unfixed/unpatched after doing a quick search on Google, but I'm not going to trawl the results any deeper tonight; if this is a dupe report or has already been fixed I might find out and update this post at some later point.
Anyway, it starts out like this: you switch your IP address to a new one (in our case that's because our Comcast modem, the one I need both arms to carry around, took a crap on us last week, so now we're working on the third iteration of this modem in the past year, with a different IP) and LastPass suddenly doesn't recognize the device you're on or the location you're at (it's not sure which), though it's the same device as always (my HP laptop, which has somehow lived another year without the graphics card destroying itself like the last one did, though pixels are beginning to blow out left and right).
When the LastPass add-on (in Firefox latest on Win 10 Pro - not an Insider build) sees your new IP address as a "new device" or "new location" (though that sounds like a bug in itself, it's not the bug I'll be talking about) it looks like this:
The text in the info bar my screen got splashed with says (emphasis mine): "LastPass doesn't recognize this device or you are at a new location. Please check you email to grant access to your new device or location."
See the part where LastPass asks me to check my email? Which means I should literally be unable to use LastPass to log into websites until that one little detail is taken care of? Heh, about that...I just ignored or dismissed the infobar (I forget which), opened the LastPass add-on dropdown menu and finished logging into my Live account like nothing had happened. No checking my email. No granting access. I just went on and used LastPass normally. Which I should not have been able to do!
After logging in, I checked for the email from LastPass just to see what it said, because them even sending it was like, totally useless. It looks like this:
This is where things get funny - if your idea of a good time is when your device gets stolen and your online security is compromised by, of all things, not the thief, but a buggy password manager. What a laugh! The email reads (emphasis mine): "Someone, hopefully you, recently tried to login to your LastPass account from a device or location that we did not recognize. We prevented access until you have reviewed the details of the login attempt."
See the part where LastPass tells me they prevented access until I could review details of the login attempt? Lies, tall tales, and made-up stories because they prevented nothing. I could use LastPass just by continuing to use it. I saw a few more infobars saying the same thing, but I just kept ignoring or dismissing them and like, logging into things. Which, again, I should not have been able to do!
I'm posting this mostly to remind myself to check the LastPass forums and search results more deeply one day for any other news of this issue, and to warn anyone else who comes across this post who might also be using LastPass.
After we brought the modem home one hot and disgusting day toward the end of last month in between ceaseless rain storms, Other Person called Comcast to help us troubleshoot it. The modem was simply not cooperating; we'd exchanged the old one to fix download speeds as low as 1.5mbps when we're supposed to be getting 75mbps down and no less than 30-45 over wifi, but even with the new modem there was no improvement.
OP wound up speaking to what, back in the day, we'd call Level 5 tech. The guy who worked with him over the phone (it was on speaker so I could listen and participate as needed) was well-spoken and clearly knowledgeable, as well as extremely patient and nice, but couldn't figure it out. He walked OP through a number of steps and processes to no avail, before he got the idea to log into our modem as us and make some adjustments.
This meant granting himself access to our gateway admin panel (the panel you normally log into over 10.0.0.0.1, or similar) which made me a bit nervous because I tend to lock things down like Fort Knox the same day we bring each modem home (and this is our third one in a year, so I've gotten rather good at practicing really tight security) but I consented simply to get the modem running right.
Well, it got running right (I'll post an image of just how fast our wifi is on the laptop we keep in the kitchen to use while we're cooking or hanging out nearby, maybe as my next post, only because it is rather funny by itself) but the possible tradeoff for that was when I logged into our Comcast account later on that night, the wifi page told me the modem was no longer ours.
But this was impossible with the way Level 5 would have left things for us. He specifically asked permission to use our last modem's broadcast name (let's say it was Cowboy, though it was not) and our last wifi password (let's say it was c0mca5t5uck5, though it was not) while he was in there making his adjustments*, which we allowed him to do for the sake of expediency.
But when I logged into Comcast later on that night instead of seeing the gateway broadcasting as Cowboy with the password c0mca5t5uck5, I saw this:
The screencap shows our gateway broadcasting with the wrong name and password. To protect the information from search indexing I'm not posting the text.
I'm like, who is L*, and what kind of password is that, because neither I nor OP would ever choose it. There is and has never been a gateway named L* in our area, so it didn't seem like it could be an odd, local mixup on Comcast's part, not to mention our wifi was literally broadcasting as Cowboy - not as L* - even as I saw this strange name and password on the page, so it also didn't seem possible a stranger had overtaken our router. And again, our Level 5 told us he used Cowboy and c0mca5t5uck5 when he went into our router to make his changes, so he should not have been at fault for why the broadcast name and password were showing up as someone else's.
At this point I was wondering if I should call Comcast as I realized I hadn't once logged into the admin panel myself to do my usual Fort Knox lockdown, when suddenly I thought to just refresh the page. Sure enough, the reloaded page showed our broadcast name as Cowboy and the password as c0mca5t5uck5. Multiple refreshes didn't bring the page back to showing the wrong name and password, so at that point it looked like the problem was solved - but not knowing what caused it has been sort of bugging me ever since.
* Edited after posting to more accurately explain what Level 5 did.
I'm not posting a full screen shot with location, latency information (48ms - actually kind of awful) and protocol (IPv6) so you'll just have to take my word for it, but the initial speed test - while we were still on the phone with Level 5 tech support after he fixed our download speed - shot up to a comparatively decent 578.75mbps:
I want this screencap framed. Better yet, I want this download speed.
Alas, it was not to be: subsequent tests show speeds as high as 150mbps (entirely on the kitchen laptop, which has the wireless N spec - the prototype of wireless N, in other words - and yet still it flies) to as low as the usual 30-45mbps on other devices around the house, but hey, I can look at this screencap, at what was for a few seconds, and dream.
It's not an unusual speed in South Korea, after all. And obviously it's possible here. The price, though, probably isn't within reach for most of us.