not much

  • 366 Posts
  • 1.05K Comments
Joined 2 years ago
cake
Cake day: December 8th, 2022

help-circle

  • I did lots of reading about this and am still wondering why someone would want to opt for catch-all domains over aliases. Catch-alls seem highly susceptible to spam and while I haven’t actually done any email aliasing yet,

    I’m using catch-all since years and no spammer has ever made up a new email alias to spam me.

    it doesn’t seem to take much effort to make a new alias if you have a plan with unlimited aliases.

    That depends. The moment you are in a shop without your phone/email and they really want an email address you can simply write down their_company_name@your_email_domain_name for them without having to compromise anything.



















  • lemmyreader@lemmy.mlOPtoTails@lemmy.mlTails - Tails 6.4
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 days ago

    How does making a keyring file work ? I tried it by importing the signing key into my keyring and then ran gpgv tails-amd64-6.4.img.sig tails-amd64-6.4.img which also gives : gpgv: Can't check signature: No public key

    Found this, which appears to suggest to use other verification methods : https://tails.net/contribute/design/download_verification/#index2h1

    OpenPGP verification instructions

    We removed the instructions to verify downloads with OpenPGP because:

    Without advanced knowledge of OpenPGP, verifying with OpenPGP provides the same level of security as the JavaScript verification on the download page, while being much more complicated and error-prone.

    None of our personas would have enough knowledge of OpenPGP to use the OpenPGP Web of Trust with confidence.

    Providing basic (and never exhaustive) instructions has proven to be very time consuming to our help desk and technical writers. See #17900.

    We still explain how to verify our signing key using the OpenPGP Web of Trust in the installation instructions from Debian, Ubuntu, or Mint using the command line and GnuPG because Debian derivatives come with trusted OpenPGP keys that can be used to create a path to our signing key.











  • Yes, go ahead and file the bug. And as others mentioned already, the custom screensaver modifications of XScreensaver like for LM may have bugs. The author of XScreensaver has been complaining about this several times.

    The bug you found looks similar to this one :

    Unlocking a machine locked with Xfce’s screensaver xfce4-screensaver has long been a simple matter of turning two monitors on at the exact same time. That makes Xfce4-screensaver versions prior to 0.1.9 segfault and crash - leaving the machine unlocked. This very unfortunate Xfce bug #16102 has been open since October 29th 2019 and we have pointed fingers at it several times before. Xfce developer Sean Davis has finally closed this gaping security hole. He explained that the embarrassingly long delay before this security vulnerability was addressed was due to “real life conflicts” in a brief comment on March 22nd. He did not elaborate and we did not ask for further details since it is likely none of our business.