(评论)
(comments)

原始链接: https://news.ycombinator.com/item?id=41596466

多个域可以为 GitHub 等组织提供各种好处,使他们能够分隔营销或安全操作等敏感活动。 拥有众多的域名可以让企业保持良好的声誉,避免与其主域名相关的垃圾邮件行为带来的潜在问题。 然而,滥用多个域名(例如 Amex)可能会导致混乱并损害其形象。 创建不同的网站来宣传软件即服务 (SaaS) 产品,而不是将它们合并在一个域下,可以有针对性地向欧盟 (EU) 用户发送同意书。 这符合《通用数据保护条例》(GDPR),涉及数据保护官员任命、用户数据删除和数据取出等任务,以及与合规实施相关的费用。 这些步骤旨在确保隐私并防止潜在的数据泄露。 此外,持有单独的 IP 地址构成个人身份信息 (PII),需要在灾难恢复过程中小心处理,特别是从备份恢复数据,同时在备份创建后保持受影响个人信息的匿名化和删除。 此外,尽管另有说法,采用网络钓鱼技术可能会欺骗不太懂技术的用户。 诈骗者致力于设计新颖的方法来针对普通互联网用户而不是经验丰富的专业人士。 冒充来自 PayPal 等信誉良好来源的电子邮件仍可能导致用户提供敏感详细信息,从而造成经济损失或身份被盗。 最后,信任电子邮件中的链接或认为电子邮件内容本质上合法会因网络钓鱼尝试而带来风险。 为了应对这些威胁,个人在遇到意外电子邮件时必须保持谨慎,尤其是那些要求立即回复或采取行动的电子邮件。 在这方面,必须遵循在线安全的最佳实践,例如不要打开附件或单击电子邮件中的未知链接。

相关文章

原文


Do people really fall for scam like that?

First, I assume the author knows the email came from github, as the screenshot does not show this very clearly. If that's the case:

Red flag #1: email links to a variation of real domain. If you don't have information on who github-scanner.com is, it is pretty safe to assume it's a scam , just because it sounds like a real website.

GIANT Enormous Huge Red Flag #2: captcha asks you to types command in shell. I have no comment on how naive one must be to do this.



It’s a numbers game.

Nobody is perfect. The more features of credibility, most likely there will be a higher percentage of conversions. But not everybody has excellent vision, is not time-pressured, and is not tired/exhausted.

There are lots of conditions that make otherwise difficult fraud targets more easy to trick.

And if it can be done at large scale / automated, then small conversion rates turn into many successful frauds (compromised accounts).



I think they’re hoping for coincidences and the higher the numbers the more likely they’ll find one.

I got a real letter from the IRS two days before I got the scam message on my answering machine. The timing was uncanny and I might easily have fallen for it, had I not already dealt with it.

It’s the same for the Chinese language calls, if you speak Chinese it really resonates.

There was a scam in the 90s where you’d call a number and they’d give you sports betting advice. They’d do it for free as a promotion trying to sell their service when you won. They’d tell half the callers bet team A and the other half team B. The numbers made it work.

“Splitting games 50-50 like that—known in the biz as "double-siding"—is the oldest trick in the handicapper's very thick book. That way he knows he has at least some happy customers coming back. “

https://vault.si.com/vault/1991/11/18/1-900-ripoffs-the-ads-...



Agree, I once fell for a scam that I think I otherwise wouldn't because of string of circumstances: Being tired and stressed, it being Christmas time and I had actually ordered stuff but also because I had just upgraded iOS to the first version that put the address bar in Safari on the bottom of the screen instead of the top so I forgot to check the domain!

I've since changed the address bar back to the top…

In the end I didn't loose anything but it was a good wakeup call for sure.



Thanks for this summary. People often forget they (hopefully) have grandmas and themselves sometimes making mistakes as well for -- whoever knows what reason. Sometimes.



If this was within my first year of owning a GitHub account, I would absolutely fall for this.

It's not much different from setting up your ssh key - something that you have to do; and new users also go through this workflow by copy pasting commands that GitHub sends them.



A prime example how all the paranoid security hoops can easily make things more insecure in aggegate.

Since Microsoft embracing and extending it, GitHub has become one of the worst offenders.



A few weeks ago someone opened an issue in one of my repos. In under a minute two accounts replied with links to file lockers asking the user to download and try some software to solve their issue. No doubt it was malware. I promptly deleted the comments and reported the accounts to GitHub.

I wouldn’t have fallen for such an obvious ploy, but the original asker seemed like they weren’t particularly technical, judging by the sparse GitHub history and quality of the question. I could see them perhaps falling for that if they were uncritical and too eager to try anything.



I just don't get it, how hard it could be? How expensive this could be? Because lots of times they just pay these damages to the customer, because no one knows how this very secure credit card data was compromised. This baffles me. Someone, please enlighten us, there must be a valid reason - at least from an angle.



Having a bunch of different domains can serve multiple purposes.

In GitHub's case, they already have githubusercontent.com to avoid serving untrusted stuff from their own github.com domain.

Sending marketing or security scanner (potentially very spammy) notification emails from separate domains can help with reputation too, to avoid your main domain getting marked as spam.

These are all legit; Amex having 20 different of domains, half of which smell like phishing, and still sending emails from other domains is just incompetence. Something like marketing people or someone dealing with strategy deciding to do stuff in a certain way, with nobody technical in the room to tell them why that would be a problem. As an example, a friend of mine's organisation wanted to do a SaaS website for their niche, and a separate website to advertise the SaaS (separate domain, visual identity, everything).



My theory for most of these cases: they would need permission from who knows what department(s) to set up a subdomain of the main domain for their project, and it's easier to just purchase a new domain for the team/project.



I'm old enough to remember ILOVEYOU. During years after that I have seen millions and millions thrown into educating users not to click on wrong things.

Last month I was in conference where the keynote was from CEO of cyber security company. The whole point of the speech was that we need more money because in some cases more than 80% users still fall into email scams. My very serious question to the speaker was - if after many millions and almost 25 years more than 80% users still click on wrong links, then maybe we do something really wrong?



We are, but people want convenience.

Try to get a company built around Word to use another tech that doesn't requires running unsigned macros from emails...

You literally can't, they lough at you for saying things like "don't use Microsoft"



They measure by clicks… but clicking a link doesn't mean you'll follow through and put in your username, password, and 2fa code.

Ultimately he's a businessman seeking for more money. Doesn't mean he can be trusted.



In my opinion, these products are nothing but scams. I can’t use any links from work emails on my phone because I can’t see the domain of a link without previewing the page. IT told me I needed to change system-wide settings to disable previewing webpages in every app on my phone. Not happening.

Fortunately, my work email supports IMAP, so I can use a script to scan my inbox for fake phishing emails and delete them.



We are not not doing anything wrong, but we are completely neglecting the attacker side.

All our actions are defensive.

Look at our physical security. Basically nothing is reasonably protected. 99% of stuff (buildings, locks) can be broken into with tools available in any home depot.

The key reason why it doesn't happen that much is because it's possible to find the attacker.

Why can any scammed just create a website without any traceability? It wouldn't be foolproof, but it would raise a bar.



> Why can any scammed just create a website without any traceability?

because jurisdictional challenges.

Not to mention that this very same traceability would be abused by some other authoritarian gov't to track down dissidents for example.

There's no real way to systematically have good security, if the human element is the weakest link tbh. Securing windows is not a technical problem, but a social and educational one.



More like no will.

Does the domain/server implements required level? No? Block connection. Dtto email with automatic response.

Is your IP in a botnet? Cut it off.

Edit: I already get blocked connection (on target site) because EU regulation is too onerous. I get reminded on basically every Google search I am being censored (Some results may have been removed under data protection law in Europe).

Completely doable.



> I already get blocked connection (on target site) because EU regulation is too onerous

More like "we want to track every single user coming to our website without giving them the option to not be tracked".



You can serve consent form only to the connections from EU.

I have been part of se several GDPR compliance projects and it's the other stuff that's the problem.

Data protection officer (recurring cost, even though it is only a part of a job, not full time position) , user data deletion and user data take-out. Compliance is not free. If system wasn't designed from the beginning, it's really expensive to add it.

Restore from backup after disaster recovery - make sure you anonymize/delete people who were deleted after backup was made.

BTW, IP address is PII, so...

Honestly, it would be cheaper to buy everyone in EU VPN.



> You can serve consent form only to the connections from EU.

Why? While I get that, if tracking is part of someone's business model, they want to track as many people as possible, I doubt it would be illegal to give also people that aren't in the EU the option to not be tracked. If it really would be so expensive to be compliant while also differentiating between users connecting from the EU and users connecting from outside the EU, why not just give everyone the option to choose if they want tracking as a measure to cut compliance cost?



You don't need to bomb anyone.

Add IP rules at cables inside and out of let's say EU and block it there.

Same way we deal with any non-compliance thing. You can't import it.

Your server/domain doesn't satisfy requirments. Either the originator complies or not (e.g. through trusted third party).



No geolocation is needed. And even if it was, these are technical problems, inherently solve able.

So far, we are building walls and replacing mortar with a new one, while attackers bombard us with complete impunity. This is never going to work.

This would of course need new extensions /protocols (even simplest would require authentication envelope around encrypted traffic).



The whole point is to move from technical solution (i.e. current approach) to legal one.

Not a single response had anything to do with either problem ITA or my comment.

I am not sure if you are troll, 10 y/o or gpt1, but have a nice day.



> GIANT Enormous Huge Red Flag #2: captcha asks you to types command in shell. I have no comment on how naive one must be to do this.

I guess critical thinking of devs and wannabee devs has been softened by all the `curl