505
lemmy.fmhy.ml is gone [update from the team] (very.bignutty.xyz)
submitted 3 years ago by to c/fediverse@lemmy.world
177 comments fedilink hide all child comments
 

An update:

  • fmhy.ml is gone, due to the ongoing fiasco with mali government taking all their .ml domains back
  • As such, lemmy.fmhy.ml is also gone, we are currently exploring ways to refederate (or somehow restart federation entirely) without breaking anything substantial
  • We have backups, so don't worry about data loss (you can view them on other instances anyway)

Currently, we have fmhy.net and are exploring options to somehow migrate, thank you for your patience.

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 3 years ago (9 children)

Damn, lemmy.zip, eh? If that instance is public, I don't see that being a good thing.

Tons of businesses, people, etc, are all banning .zip and .mov TLDs for security purposes. I've personally banned all those domains from my network as well.

Bold move.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 2 points 3 years ago (6 children)

    What's the issue with those TLDs?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 16 points 3 years ago (4 children)

    See https://youtu.be/GCVJsz7EODA and https://youtu.be/V82lHNsSPww

    There are a few problems, but I believe the biggest issue is that .zip and .mov are valid and common file extensions, and it's common for people to write something like 'example dot zip' or 'attachment dot mov' in emails, tweets, etc. Things like email clients have features where they automatically convert text that looks like a web address into clickable links. So now, retroactively, all those emails etc suddenly have a link, where they used to just have text, and the domains that are equivalent to those previously benign file names are being purchased by nefarious actors to exploit people unaware of the issue.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 0 points 3 years ago* (1 child)

    But there's only an issue if the software you're using auto linkifies the domain. They often don't and won't. This seems like a hypothetical problem that probably doesn't exist for most major software. I certainly know no email software is gonna auto linkify this.

    If you're curious, you can see if whatever software you're viewing this post in auto linkifies (neither are for me): hshshssu.zip iwuf8aowk.mov

    (And if we're manually linkifying, then you don't need to use the new TLD. Eg, not-a-virus.zip.)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 3 years ago

    At 1:30 in that second video, he shows that YouTube already converts dot zip domains, even in old comments that predate the domain's existence. At 3:19, he shows/mentions Twitter, Reddit, Facebook, and LinkedIn. I would consider those major platforms. And keep in mind, it only takes one person downloading one file to cause major damage - the LMG hack was due to someone downloading and trying to open a fake PDF that was sent via email: https://youtu.be/yGXaAWbzl5A.

    So yes, not everything does or will auto convert the links, but I think you are underestimating the potential for issues here.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 years ago

    https://www.trendmicro.com/en_us/research/23/e/future-exploitation-vector-file-extensions-as-top-level-domains.html

    Actually really huge security threats. It's a very good idea to block them. I especially did because my girlfriend works for the government and does some secret stuff that can't really get out, and she deals with a ton of real .zip files. I think everyone regardless of who they are should make sure to block them.

  • permalink
  • fedilink
  • source
  • parent