In their defence I assume most of these terminals were planned for pre-9/11 security.
Only, in my case, I also need to open my bag, unpack laptop sleeve, extract laptop from sleeve and put into bin, unpack iPad sleeve, extract iPad from sleeve and put into bin, extract power bank case, extract power bank and put into bin.
If you every fly out of Milwaukee, they have an area for doing that:
Many airports have benches just past the security checkpoint which are convenient for putting your shoes back on and putting stuff back in your pockets.
Tbh I’ve never been at an airport where this wasn’t the setup.
This is EWR:
At such stations, there is a TSA agent behind the conveyor who instructs you when to push your bin forward. I think they are trying to time things so your bin goes forward at about the time you will get through the screening process.
Yes. They don’t want your bags into the bag scanner much before you get through the people-scanner. Otherwise there’s an overflow of bags at the output end when anyone needs extra people-scanning.
BTW, this is the scanner I frequently see at airport checkpoints. What amazes me is that so many bins disappear into that scanner before emerging on the far side, much more than the machine seems capable of holding. I almost wonder if the machine is sending them downstairs and back up.
I feel your pain–working for the military, I had at least one site that had an 18-digit password! (I’m not kidding) which also had to be changed every 90 days, no repeats or lookalikes, and I had 18 different sites. I had to keep a book with all of them, along with dates so I could keep up
That “recombobulation area” text at the top isn’t a caption, it’s an actual sign in the airport. That’s all I was going for. The airport put that up years ago as a joke.
I just spent 3 nights in the hospital.
There was a remote that handled calling the nurse, turning several of the lights on and off, and the TV. It also had a numeric keypad (for what? Entering nuclear codes?).
What it did NOT have was any controls for raising or lowering the bed. Those were on the rails. Above the level of my shoulders i.e. unreachable without doing some twisting that I was explicitly NOT supposed to do.
Lose the fucking numeric keys and put 3 buttons to raise / lower the head and foot, as I’ve seen elsewhere.
Oh, and my feet were jammed quite painfully against the footboard on the second night where they had not been the first night. It wasn’t until early morning where a nurse figured out how to move the footboard. There is a "long " button where the patient cannot see or access it, and evidently the housekeeping staff is trained to put that back into default position, because I had the same issue the third night and it was my husband who figured that out.
Argh… If they’re able to enforce a no-lookalikes policy, then those aren’t passwords.
Holy cow. When I was in the navy we had cypher locks to get into the secure spaces, four digits on five rocker keys to get all ten available. One location I had to memorize six of them that changed every month. Two things made it easier,
Having some experience in cryptography, I share your sentiment.
There should be no way for the system to interpret “scudsucker” and “scudsucker2” as similar. I can accept they compare the hash of your previous password to ensure you are not just reusing the same password, but those two are fundamentally different in cryptographical calculations.
I mean, using a random string, we get an MD5 encoding of
cd384fcf9378a444eb541fd1d96cfb18
Adding a “2” to the end, we get
5715b80d7fb8f865dfd802dc6a58e316
And MD5 is hardly the best encryption available.
The system takes the plaintext of the proposed password and computes the hashes of a bunch of different variants of it. If any of those match the hash of the previous password, the system rejects the proposed password.
This seems unlikely, IMHO… granted I am not an expert.
Let’s say, my password was “scudSucker07_1”
Using just MD5, and not SHA256, the permutations of,
is both incorrect and unpredictable, given the context.
None of this is going to show up on “rainbow tables” unless there has been a password breach, and in any case I use a different varient for every site where I need to enter a password.
With SHA256, such a password will probably only be cracked in around 2 years of serious effort, and if a hacker wishes to access my SD account, well… best of luck.
When you updated to this, the system could easily check if any of these were a previous password:
scudSucker07_1
scudSucker07_
scudSucker07_0
scudSucker07_2
scudSucker07_3
…
0scudSucker07_
1scudSucker07_
2scudSucker07_
3scudSucker07_
…
cudSucker07_1
cudSucker07_10
cudSucker07_11
cudSucker07_12
…
0cudSucker07_1
1cudSucker07_1
2cudSucker07_1
3cudSucker07_1
…
And so on for whatever pattern the implementor cares to process.
I’ve found that many systems do simple tests by omitting the first or last character of the proposed password and rainbowing all possible characters prepended and appended. I have not found any system that implements more complicated rainbows.
My password is a variant of my deceased cat’s name.
I think it is relatively secure, unless, by accident, no-one really, really knows me.
The cat was pretty cool, but it turned out she was not a male, and I wasn’t very ready when she gave birth to three kittens.
Her “male” name still performs part of of my complex passwords.
FWIW, while I don’t know what you do to turn it into your password, I DO know your cat’s name, and I’m just some random guy on the internet.
I doubt that.
But in any case her name is followed by a succession of numbers, letters and symbols that only make sense to myself.
So you might (arguably) know the first 5 characters, which I doubt, but you do not know the next 4, and you can’t know if I did a substitution (eg, an ampersand for an ‘a’) in the characters, in the first few characters nor where.. if I even did..
@Joey_P, what is my cat’s name?
I’l help you out. Her name was a common culinary plant. Good luck with the guessing.
Hint: I adopted her believing she was male. So she had a male name.
St George