@Snipe_AT@lemmy.atay.dev
@Snipe_AT@lemmy.atay.dev avatar

Snipe_AT

@Snipe_AT@lemmy.atay.dev

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

That… was not what I expected to follow that chain of words.

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

Thank you. I didn’t know I needed the answer to this question until now.

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

what’s your guess as to the percentage of US military spending compared to its tax revenue?

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

“have you tried turning it off and back on again?”

i.e. i’ve seen it correct itself by unsubscribing and subscribing again

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

sorry i’m missing it. why this specific TLD? can’t they just use any TLD for this and achieve the same thing? why is this a reason to block it?

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

i think i understand that part but why is this specific event “another reason to block this TLD”? can’t they just use any TLD for this and achieve the same thing? is there another inherit security issue with .zip that doesn’t exist with other domains?

Snipe_AT,
@Snipe_AT@lemmy.atay.dev avatar

gotcha ok i think i’m getting it. just to make sure i’m not missing anything, you’re saying that in this case it didn’t matter as in the end they could use any TLD and achieve the same effect.

but in general, threat actors hope to confuse people into thinking this “.zip” TLDs are only referencing local files instead of web addresses. right?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #