Mastodon 🐘

0 posts0 participants0 posts today

Colan Schwartz<a href="https://hachyderm.io/@drukqs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@drukqs</a> Yes, these are great services. I've been using the e-mail aliases with <a href="https://mastodon.social/tags/protonpass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protonpass</a> (now that <a href="https://mastodon.social/@protonprivacy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@protonprivacy</a> bought <a href="https://fosstodon.org/@simplelogin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simplelogin</a>). <a href="https://mastodon.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> <a href="https://mastodon.social/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a>

Hacker NewsWhy "alias" is my last resort for aliases — <a href="https://evanhahn.com/why-alias-is-my-last-resort-for-aliases/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://evanhahn.com/why-alias-is-my-last-resort-for-aliases/</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/alias" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#alias</a> <a href="https://mastodon.social/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://mastodon.social/tags/lastresort" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lastresort</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://mastodon.social/tags/tips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tips</a> <a href="https://mastodon.social/tags/evanhahn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#evanhahn</a>

StockbridgeArchBonnie and Clyde. <a href="https://mastodon.scot/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://mastodon.scot/tags/rough" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rough</a>

astridCanceling my subscription with <a href="https://mas.to/tags/Proton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Proton</a> and could use some advice on alternatives. I looked at <a href="https://mas.to/tags/Startmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Startmail</a> and <a href="https://mas.to/tags/Tuta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tuta</a> but I've been using Proton for <a href="https://mas.to/tags/CloudStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudStorage</a>, <a href="https://mas.to/tags/Calendar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Calendar</a>, and <a href="https://mas.to/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a>. <a href="https://mas.to/tags/AskFedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AskFedi</a> <a href="https://mas.to/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://mas.to/tags/Computers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Computers</a> <a href="https://mas.to/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://mas.to/tags/ProtonMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProtonMail</a> <a href="https://mas.to/tags/Computers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Computers</a> <a href="https://mas.to/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://mas.to/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> <a href="https://mas.to/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mas.to/tags/BigTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BigTech</a>

Thomas Guyot-SionnestHard to believe the top answer to enable <a href="https://noc.social/tags/shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shell</a> <a href="https://noc.social/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> in <a href="https://noc.social/tags/vim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vim</a> is to make the shell interactive, which obviously make significant change to how vim interacts with the shell.My solution for <a href="https://noc.social/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> is much better and can even be used to customize shell aliases loaded under vim 🙂 <a href="https://stackoverflow.com/a/79458714/969196" rel="nofollow noopener noreferrer" target="_blank">https://stackoverflow.com/a/79458714/969196</a>

Kevin Karhan :verified:<a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lispi314</a> <a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@enigmatico</a> <a href="https://transfem.social/@bunnybeam" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bunnybeam</a> <a href="https://ublog.kimapr.net/users/kimapr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kimapr</a> nodds in agreement<ul><li>I think having a proper <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#API</a> is a way to facilitate that, cuz worst-case one just slaps together some <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> in <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a>, <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fish</a>, <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zsh</a> or whatever <a href="https://infosec.space/tags/shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shell</a> and just uses <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#curl</a> to query stuff manually as this solves the whole <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebApp</a> - issue.</li></ul>And I do prefer <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> as it works fine for an ever increasing audience!<ul><li>Even if we choose to point at bad <a href="https://infosec.space/tags/UX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UX</a> / <a href="https://infosec.space/tags/UI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UI</a> combos like <a href="https://infosec.space/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GnuPG</a>, we've to also acknowledge better existing alternatives like <a href="https://infosec.space/tags/enc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#enc</a> that <a href="https://github.com/life4/enc" rel="nofollow noopener noreferrer" target="_blank">just work</a>!</li></ul>Personally, I think that everything people are expected to use if not forced to use should be <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> as licensed in a <a href="https://infosec.space/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> accredited license and be released with <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> and <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#documentation</a> to make <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reproduceableBuilds</a> and thus facilitate <a href="https://infosec.space/tags/audits" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#audits</a> by truly independent parties...<ul><li>And if that's not possible any requirement to using said things should be outlawed no matter the context! </li></ul>A unsarcastically good example is <a href="https://infosec.space/tags/S3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#S3</a>, even tho I hate <a href="https://infosec.space/tags/amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amazon</a>, they wanted <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developers</a> to integrate their <a href="https://infosec.space/tags/ObjectStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ObjectStorage</a> which necessitated an <a href="https://infosec.space/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open</a> source'd API to the point that it's <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backend</a> is inherently reproduceable, and now every halfassing <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webhoster</a> offers S3 <a href="https://infosec.space/tags/storage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#storage</a>, sometimes with bit & second-precise billing.

Techniverse BlogFix: Postfix – database /etc/aliases.db is older than source file /etc/aliasesHeute früh bekam ich bei dem Blick in die Logwatch von Postfix die Meldungwarning: database /etc/aliases.db is older than source file /etc/aliasesNaja, überrascht bin ich nicht, denn ich hab ja in den letzten Stunden ziemlich viel an dem Programm rumgespiel...<a href="https://www.techniverse.net/blog/2024/12/fix-postfix-database-db-is-older-than-source/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.techniverse.net/blog/2024/12/fix-postfix-database-db-is-older-than-source/</a> <a href="https://social.techniverse.net/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://social.techniverse.net/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://social.techniverse.net/tags/database" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#database</a> <a href="https://social.techniverse.net/tags/konfig" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#konfig</a> <a href="https://social.techniverse.net/tags/postfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postfix</a>

Kevin Karhan :verified:<a href="https://chitter.xyz/@roxy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@roxy</a> true, true...But there"s like <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> in <a href="https://infosec.space/tags/shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shell</a>|s like <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> for that.. <a href="http://github.com/kkarhan/misc-scripts/blob/master/bash/.bash_aliases" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://github.com/kkarhan/misc-scripts/blob/master/bash/.bash_aliases</a>

Bèr Kessels 🐝 🚐 🏄 🌱My alias to delete trailing whitespace in a file:dt='sed -i '\''s/[[:space:]]*$//g'\'' 'Used as `dt some-config.yml` (filename as attribute, hence the trailing space in this alias, irony)go fmt, rust fmt, prettier and many other linters and formatters will do this for me already. But not all filetypes have linters (that I want to install, remember and/or configure). So for that: dt, Delete Trailing space.<a href="https://mastodon.nl/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.nl/tags/commandline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commandline</a> <a href="https://mastodon.nl/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://mastodon.nl/tags/linuxtip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linuxtip</a> <a href="https://mastodon.nl/tags/sed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sed</a>

Kevin Karhan :verified:<a href="https://wonkodon.com/@admin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@admin</a> <a href="https://m.ai6yr.org/@ai6yr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ai6yr</a> <a href="https://bitbang.social/@profoundlynerdy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@profoundlynerdy</a> I do <a href="https://github.com/kkarhan/misc-scripts/blob/master/bash/.bash_aliases" rel="nofollow noopener noreferrer" target="_blank">even more</a> <a href="https://infosec.space/tags/cursed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cursed</a> <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> like <code>dir</code> and <code>cls</code> cuz I started out on <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MSDOS</a> and I think that <code>dir</code> is way faster to type than <code>ls -alh</code>…

Habr[Перевод] Настройка алиасов путей с помощью Node.js Subpath Imports в TypeScript проектеЯ попробовал новые Node.js Subpath Imports для алиасов путей в TypeScript проекте. Оказалось, всё не так просто!<a href="https://habr.com/ru/articles/840240/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://habr.com/ru/articles/840240/</a><a href="https://zhub.link/tags/subpath_imports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#subpath_imports</a> <a href="https://zhub.link/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://zhub.link/tags/custom_conditions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#custom_conditions</a> <a href="https://zhub.link/tags/path_aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#path_aliases</a>

Gauff 🇪🇺A <a href="https://piaille.fr/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> question about <a href="https://fosstodon.org/@simplelogin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simplelogin</a> ... if I use <a href="https://piaille.fr/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> and <a href="https://piaille.fr/tags/ReverseAliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReverseAliases</a>, the service is great but domains (even premium) are sometimes rejected because detected as "disposable".So I use my own domain (let's call it dom.be) and I register it on <a href="https://piaille.fr/tags/simplelogin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#simplelogin</a>. By doing that, I can enjoy <a href="https://piaille.fr/tags/simplelogin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#simplelogin</a> service and not be seen as using a disposable mail service.But then, my domain is "exposed": a malicious counterpart might decide to expose dom.be everywhere and start spamming stuff like "info@dom.be", "contact@dom.be", etc?Domain is registered under my name, so anonymity is lost too?Am I going too far? Is there a best way to do this?

Erik van Straten<a href="https://toad.social/@grumpybozo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@grumpybozo</a> : I don't fully agree with you.I have no personal experience with Proofpoint, but I agree that Microsoft usually messes up security.For example, it took Microsoft years to understand that bypassing ALL checks upto DMARC for senders in the user's list of "safe senders" (explicitly added, or implicitly because they were present in the user's personal address book) was one of their most stupid ideas ever (even if *that* list is long):<<< We also determined that the allowed sender and allowed domain lists in anti-spam policies and Safe Senders in Outlook were too broad and were causing more harm than good. >>> <a href="https://learn.microsoft.com/en-us/defender-office-365/secure-by-default?view=o365-worldwide" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://learn.microsoft.com/en-us/defender-office-365/secure-by-default?view=o365-worldwide</a>However, the problem here is not Microsoft or Proofpoint, but illusions created by marketeers of protocols such as SPF, DKIM, DMARC, ARC and BIMI.Initially there are always nitwits (including Bill Gates) who predict that such protocols will kill spam. As expected (by people who understand), none of them did.Then the nitwit marketeers will claim that, even if such a protocol does not stop spam, it'll kill phishing. As we know, none of those protocols did.The reasons are simple:1) Domain names are just (temporary) aliases to identities - like phone numbers. They may *seem* meaningful but are not.Usually the identity-alias relation makes some sense, but only in one direction. Most people know that google.com belongs to Google. However, having seen aka.ms or goo.gl does make at least some people believe that the .ms TLD belongs to Microsoft and .gl to Google: they do not.Typically (again) marketeers fail to understand this in general as well as the hierarchical nature of domain names. This lunacy leads to the fact that people are supposed to remember every domain name *precisely* that an organization may use (domain names have zero fault tolerance).We learned that microsoft.com belongs to Microsoft, Inc. from Redmond.However, why would (login.) microsoftonline.com also belong to that company? Which idiot "invents" such a name? Are their other servers offline or what? Why didn't they use login.microsoft.com?And why does live.com belong to them? And passport.com, outlook.com? Okay, if that's the case, then why would microsofsignin.com, microsoft.login.com, lookout.com, microsoft.fail and microsoft.wtf *NOT* belong to Microsoft, Inc?2) Most email programs hide the sender's SMTP-address anyway. As recipients typically do not get to see the originator's domain name, it may differ (unknowingly by the recipient) from the one suggested by the falsified text in the message. A different domain name may have their own SPF, DKIM and DMARC configuration set up correctly.Unfortunately those protocols are not like "nothing's lost if they don't help"; they cause significant amounts of collateral damage.SPF breaks email forwarding (there's an awkward "fix" for that problem - that someone else has to implement), and mailing list servers often break DKIM signatures. This has lead to the DMARC "fix" that if one of the SPF and DKIM checks fails, that's just fine. Which weakens the whole idea.Every email admin has their own interpretation of optimal settings, such as what to do if an email originator specifies - (minus) or ~ in their SPF record. And they may "tune" them whenever they feel that it"s right.The recipient usually does not know what the sending mail server asks the receiving mail server to do in case of SPF etc. errors or warnings, nor does the recipient usually know whether their receiving mail server honors such requests (and neither does the sender). Mail "should not be lost for frivolous reasons" but in practice it does.Approximately half of the mails from the cryptography mailing list end up in my spam box, and my email address was unsubscribed from the full disclosure mailing list because of the excessive amount of bounces their server received from my internet provider's mail server.Nested SPF DNS records may lead to unecpected failures because someone else changes a record leading to a list that becomes too long.And this list goes on. It's a mess - while the problems that supposedly should have been solved, have not.In the end: the easier impersonation is, the weaker authentication becomes. I.e. reliable authentication is HARD - in particular remote/online.<a href="https://infosec.exchange/@fuzztech" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuzztech</a> <a href="https://istoleyour.pw/@compuguy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@compuguy</a> <a href="https://infosec.exchange/tags/Authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authentication</a> <a href="https://infosec.exchange/tags/Impersonation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Impersonation</a> <a href="https://infosec.exchange/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SPF</a> <a href="https://infosec.exchange/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DKIM</a> <a href="https://infosec.exchange/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DMARC</a> <a href="https://infosec.exchange/tags/ARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ARC</a> <a href="https://infosec.exchange/tags/DomainNames" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DomainNames</a> <a href="https://infosec.exchange/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a>

Erik van Straten<a href="https://infosec.exchange/@tasket" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tasket</a> wrote:<<< Checking the spelling of domains is all people have, in addition to https and bookmarks. >>>Agreed.However, that does not scale. It makes no sense to have every person who uses the web to figure out who a domain name belongs to.Something that was not very reliable when 'whois' *did* help, but 'for privacy reasons" whois was rendered totally useless.We need third parties, trusted by *US*, internet *USERS*, to:1) reliably determine "who* is responsible for a domain name2) include an indication how trustworthy each specific identity verification process was performedThey need to be supervised NOT by commercial parties who, and/and: • hand out certificates THEMSELVES; • create a browser with the biggest market share; • are a huge cloud provider; • allicated a zillion stupid TLD's that enormously add to the confusion of users; • claim they're "not evil" (yeah right).<<< As for domain registration, you yourself said domains are very cheap. So not covering common permutations is also mindlessness, coming from the other direction. >>>It is impossible to cover all potentially misleading permutations; there simply are way too many possibilities.<<< ANY expectation the people won't look at the domain (knowing who you communicate with!) is playing with fire. Unfortunately its incredibly common; I've seen only one instance of an expert suggesting this to users over the past 15y. So phishing gets worse and we burn. >>>Exactly - except not we, but regular users.<<< Mostly I think IT pros just want to press buttons, install new gee-whiz-ware and not ever be bothered with communicating effectively with end users. When they argue that users are too inattentive, they are making the perfect the enemy of the good. >>>Indeed. And very unfortunate for regular and less "cybersecurity aware" people, because digitalization eliminates the posdibilities to do business and banking offline.<a href="https://infosec.exchange/tags/Phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Phishing</a> <a href="https://infosec.exchange/tags/DomainNames" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DomainNames</a> <a href="https://infosec.exchange/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a> <a href="https://infosec.exchange/tags/Pseudonyms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pseudonyms</a> <a href="https://infosec.exchange/tags/AnonymousWebsites" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AnonymousWebsites</a> <a href="https://infosec.exchange/tags/CyberSecurityAwareness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberSecurityAwareness</a> <a href="https://infosec.exchange/tags/SecurityAwareness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecurityAwareness</a> <a href="https://infosec.exchange/tags/SelfishAdmins" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfishAdmins</a>

Erik van Straten<a href="https://westergaard.social/users/kasperd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kasperd</a> wrote:<<< The CA system is and always has been flawed. >>>So are passports, but I know of nothing better.One of the major problems with CA's is that not CONSUMERS (or consumer organizations) are demanding reliability of certificates, but increasingly that commercial organizations are "taking care of this on our behalf".<<< What kind of certificate a site uses has little impact on security when the users most likely to be targeted don't even know how to view the certificate. >>>That is exactly why I also demand that the UI changes, and that irrelevant details (such as serial numbers, public keys etc.) are not shown on the end user interface (a "Details" button is desirable for experts).End users only need to know three things:1) identifying information, in human readable format (not CN= etc.), of the person or organization responsible for a website;2) The reliability of the identification process leading to the information in 1;3) The reputation of the responsible entity (in offline life this is also something people have to figure out for themselves, so we're more used to that than figuring out, given a domain name, who the owner is).<<< Here is an example of one very sensitive site which uses a Let's Encrypt certificate: <a href="https://www.mitid.dk/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mitid.dk/</a> >>>More oops: <a href="https://internet.nl/site/mitid.dk/2866949/#control-panel-10" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://internet.nl/site/mitid.dk/2866949/#control-panel-10</a>Technically a domain name is fine. However, domain names are not suitable for human beings *because* criminals are exploiting human weaknesses.I know of an increasing number of health and other critical websites using DV certs. Why? Cheap, auto-update, and browsers (deliberately) hide any differences with more useful certificates. So why bother?Such a certificate (together with an associated private key) indeed reasonably makes sure that, if you tap any link and end up with "<a href="https://www.mitid.dk/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mitid.dk/</a>" in the address bar of your browser (fully visible when tapping it), your browser really has an E2EE connection with a server having the domain name "www.mitid.dk".<<< Is it a problem that the site uses a Let's Encrypt certificate and not some other certificate? Maybe it is, but I can assure you that's the least problem. >>>Here's my slogan: authentication is always weak if impersonation is easy.Most relevant for a visitor is NOT that they're actually visiting some website identified by "www.mitid.dk", but that they're not being fooled by a look-a-like website with whatever domain name that they may or may not know by heart.If you're walking in the center of a city and see an ATM, then most of us presume that, after we stick our bank card in it and enter the PIN, it will spit out money and return our card; we do no expect it t keep our card, not give us money and have our account drained.I.e. if it reads ATM then we're used to the fact that it IS a legitimate ATM.If a building reads "Bank XYZ", then in practice it will not be rented by a group of criminals.Location based authentication does NOT apply to the internet. You never know where a server is located, who owns it, who rents it and which people have access to it. Even if you can look up an IP-address, that may belong to a proxy (CDN) server. You have no idea what things look like behind that proxy.For example, for their cheap offerings Fastly puts 100 mostly unrelated domain names into a single certificate and reuses key pairs for many certificates for multiple years.This is weak E2PE: (your) End To Proxy Encryption.Example: <a href="https://crt.sh/?id=13113973072" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://crt.sh/?id=13113973072</a> (see below the Subject Alternative Names). Don't tap "Subject Public Key Info", as the connection will time out while the server tries to find all records of certificates with the same public key.It's misplaced trust.A mostly criminal internet *might" be okay if we wouldn't move critical services from offline to online. I predict that EDIW (aka EUDIW) will become a disaster - because authenticating yourself mandates that the entity who authenticates YOU, is trustworthy. If you're not even sure who that is, chances are high that it's an AitM who will steal your identity.<a href="https://mas.to/@tasket" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tasket</a> <a href="https://infosec.exchange/tags/Trust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trust</a> <a href="https://infosec.exchange/tags/DomainNames" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DomainNames</a> <a href="https://infosec.exchange/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a> <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CDN</a> <a href="https://infosec.exchange/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a> <a href="https://infosec.exchange/tags/Fastly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fastly</a> <a href="https://infosec.exchange/tags/EDIW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EDIW</a> <a href="https://infosec.exchange/tags/EUDIW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUDIW</a> <a href="https://infosec.exchange/tags/eID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eID</a> <a href="https://infosec.exchange/tags/Identity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Identity</a> <a href="https://infosec.exchange/tags/Authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authentication</a> <a href="https://infosec.exchange/tags/Impersonation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Impersonation</a> <a href="https://infosec.exchange/tags/AitM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AitM</a> <a href="https://infosec.exchange/tags/MitM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MitM</a>

Erik van Straten<a href="https://mastodon.sdf.org/@msquebanh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@msquebanh</a> : it is good to stand up for yourself. But it is better to stand up for those who can't or don't know how to do that (from what I've read about you, you *do* stand up for others as well).I'm very sorry to read that you lost your dad under horrible circumstances.W.r.t. standing up for others (not intended to teach anyone a lesson, just letting the reader know who I am): I have zero experience with whales, but usually I know (or can figure out) and understand what happens "under water" when money makers claim things like "military grade IT security".Internet is getting unsafer every day, leading to innocent people getting robbed by cybercriminals (see <a href="https://www.thecut.com/article/amazon-scam-call-ftc-arrest-warrants.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.thecut.com/article/amazon-scam-call-ftc-arrest-warrants.html</a> and/or Joanna Stern warning for iPhone theft in <a href="https://youtu.be/QUYODQB_2wQ" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/QUYODQB_2wQ</a> and <a href="https://youtu.be/tCfb9Wizq9Q" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/tCfb9Wizq9Q</a> - still insufficiently fixed: here's another sad personal story regarding account take over: <a href="https://infosec.exchange/@tamarasellman@social.seattle.wa.us/112460188315248070" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://infosec.exchange/@tamarasellman@social.seattle.wa.us/112460188315248070</a>).And when I get the feeling that what politicians or other influencers try to convince less informed people about, is just one side of a story that affects many of us, or is even way beyond the truth, I'll dig in and try to find as much insightful info from any party and make up my mind (that doesn't imply that I always get it right, but looking at things from multiple perspectives has helped me a lot as a security guy).In any case, don't rely on a single statement (including from me, either actually or seemingly): check reputation before granting trust. Checking reputation necessitates that you're sufficiently sure that someone is who they say they are - which usually is the *biggest* challenge online (internet and phone).<a href="https://social.seattle.wa.us/@tamarasellman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tamarasellman</a> <a href="https://infosec.exchange/tags/Helping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Helping</a> <a href="https://infosec.exchange/tags/InnocentVictims" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnocentVictims</a> <a href="https://infosec.exchange/tags/AnimalRights" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AnimalRights</a> <a href="https://infosec.exchange/tags/Anonymous" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Anonymous</a> <a href="https://infosec.exchange/tags/Anonimity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Anonimity</a> <a href="https://infosec.exchange/tags/Pseudonyms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pseudonyms</a> <a href="https://infosec.exchange/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a> <a href="https://infosec.exchange/tags/Authentic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authentic</a> <a href="https://infosec.exchange/tags/Authenticity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Authenticity</a> <a href="https://infosec.exchange/tags/Trust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trust</a>

Brian HayesLittle snippets of aliases are something I take the time to go hunting for from time to time. Over time, these bits of shortcuts and automations add up, eventually making you look like some sort of wizard to those unfamiliar with the Command Line. Here's one of my favorites, which makes a directory and immediately navigates into it:alias mkcd='{ IFS= read -r d && mkdir "$d" && cd "$d"; } <<<' Care to share your favorite bash aliases below? <a href="https://mas.to/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://mas.to/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> <a href="https://mas.to/tags/scripting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scripting</a> <a href="https://mas.to/tags/automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#automation</a> <a href="https://mas.to/tags/workflow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#workflow</a>

Renaud Lifchitz :verified:<a href="https://infosec.exchange/tags/Proton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Proton</a> Mail Introduces "<a href="https://infosec.exchange/tags/Email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Email</a> <a href="https://infosec.exchange/tags/Aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aliases</a>" for Heightened <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://restoreprivacy.com/proton-mail-introduces-email-aliases-for-heightened-privacy/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://restoreprivacy.com/proton-mail-introduces-email-aliases-for-heightened-privacy/</a>

jorgesumleПсевдонимы для упрощения решения задач в Bash<a href="https://freakspot.net/ru/psevdonimy-dlja-upro%C5%9Denija-re%C5%A1enija-zada%C4%8D-v-Bash/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://freakspot.net/ru/psevdonimy-dlja-upro%C5%9Denija-re%C5%A1enija-zada%C4%8D-v-Bash/</a><a href="https://mastodon.ml/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> <a href="https://mastodon.ml/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a> <a href="https://mastodon.ml/tags/ru" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ru</a>

Susan Larson ♀️🏳️‍🌈🏳️‍⚧️🌈<a href="https://mastodon.online/tags/GOP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GOP</a>, <a href="https://mastodon.online/tags/FoxNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FoxNews</a> <a href="https://mastodon.online/tags/falsely" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#falsely</a> <a href="https://mastodon.online/tags/claim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#claim</a> <a href="https://mastodon.online/tags/megachurch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#megachurch</a> <a href="https://mastodon.online/tags/shooter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shooter</a> is <a href="https://mastodon.online/tags/trans" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trans</a>. <a href="https://mastodon.online/tags/Lawenforcement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lawenforcement</a> <a href="https://mastodon.online/tags/officials" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#officials</a> said Moreno previously went by multiple <a href="https://mastodon.online/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aliases</a>, including using both <a href="https://mastodon.online/tags/male" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#male</a> and <a href="https://mastodon.online/tags/female" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#female</a> <a href="https://mastodon.online/tags/names" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#names</a>, but said there is <a href="https://mastodon.online/tags/noevidence" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#noevidence</a> she was <a href="https://mastodon.online/tags/transgender" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transgender</a>. <a href="https://mastodon.online/tags/Women" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Women</a> <a href="https://mastodon.online/tags/Transgender" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Transgender</a> <a href="https://mastodon.online/tags/LGBTQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LGBTQ</a> <a href="https://mastodon.online/tags/LGBTQIA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LGBTQIA</a> <a href="https://mastodon.online/tags/Conservatives" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Conservatives</a> <a href="https://mastodon.online/tags/Extremism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Extremism</a> <a href="https://mastodon.online/tags/Fascism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fascism</a> <a href="https://mastodon.online/tags/RepublicanParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RepublicanParty</a> <a href="https://mastodon.online/tags/Hate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hate</a> <a href="https://mastodon.online/tags/Bigotry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bigotry</a> <a href="https://mastodon.online/tags/Violence" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Violence</a> <a href="https://mastodon.online/tags/Genocide" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Genocide</a> <a href="https://mastodon.online/tags/Discrimination" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Discrimination</a> <a href="https://mastodon.online/tags/Transphobia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Transphobia</a> <a href="https://mastodon.online/tags/ThePartyOfHate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThePartyOfHate</a> <a href="https://epgn.com/2024/02/14/gop-fox-news-falsely-claim-megachurch-shooter-is-trans/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://epgn.com/2024/02/14/gop-fox-news-falsely-claim-megachurch-shooter-is-trans/</a>

Recent searches

Search options

Administered by:

Server stats:

#aliases