Technology

34828 readers

21 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

MinutePhrase@lemmy.ml

188

Bypassing airport security via SQL injection (ian.sh)

submitted 2 months ago by jaromil@fed.dyne.org to c/technology@lemmy.ml

15 comments fedilink hide all child comments

cross-posted from: https://fed.dyne.org/post/228188

you are viewing a single comment's thread
view the rest of the comments

[–] haydng@lemmy.nz 31 points 2 months ago (1 children)

I'm sorry, but WTF is

We did not want to contact FlyCASS first as it appeared to be operated only by one person and we did not want to alarm them.

They are the company, running the thing. You are going to alarm them a whole lot more by going to the damn DHS. Like, I think DHS and TSA probably do need to know about this, but why not start with the actual intimately responsible party?

[–] sorter_plainview 7 points 2 months ago

I also didn't understand the logic here. Why did they "did not want to alarm them"? Is it because a one person company can simply fix the issue and not report to any other authority? What is the rationale behind it?