Heads up that we’ve bumped the UI up to 0.18.2-rc.1, which should resolve the current exploit that was seen on lemmy.world.

We’ve also logged out all currently logged in users as part of it, so you’ll need to login again.

  • Mongostein@lemmy.caEnglish
    9·
    3 years ago

    I was having trouble figuring out how to sign out and back in with mlemmy. Did it work?

    Edit: looks like yes. For anyone else having this problem, I went to the profile button, opened the gear in the top right corner, then “accounts” -> “edit account” then didn’t change anything and just hit “save.” It must have worked to log me out and back in.

  • Borgzilla@lemmy.caEnglish
    5·
    3 years ago

    Fail fast, fail often. They have handled the issue like bosses. This project is going places.

  • CorruptBuddha@lemmy.caBannedEnglish
    5·
    3 years ago

    For anyone having issues logging into Jerboa, I had to clear my cache before it would work.

  • nbailey@lemmy.caEnglish
    5·
    3 years ago

    Very impressive incident response and patch turnaround time – Kudos to the admins, devs, and sysadmins!!

  • m-p{3}@lemmy.caMEnglish
    4·
    3 years ago

    Ah so that’s why Connect for Lemmy was unable to display my frontpage despite being “logged in”. Signin out of the account and signing back in fixed it

    • dan80@lemmy.caEnglish
      2·
      3 years ago

      Same problem on Memmy. Signed out than back in, everything worked properly.

  • EastofEdson@lemmy.caEnglish
    4·
    3 years ago

    That explains why I had to sign in again. I was thinking it was a bug in the Connect app. Good to know it wasn’t.

  • TableCoffee@lemmy.caEnglish
    3·
    3 years ago

    Thanks for doing that. I was wondering why my multiple Lemmy apps weren’t loading my account. Then saw the news.

    I appreciate you going ahead and logging out all users anyway. Just needed to remove and add accounts again in the various apps (using so many until one feels like the best for me!). But thanks for taking those steps!

  • neb@lemmy.caEnglish
    2·
    3 years ago

    I went looking to re-attempt 2FA setup. After enabling it in the options, the link that for 0.18.0 would trigger an event to add it to AndOTP (instead of just providing the secret) isn’t showing up at all. (If that makes any sense in my current decaffeinated state)

    • Shadow@lemmy.caOPMEnglish
      3·
      3 years ago

      I’ll take a look in a bit but might be a new bug.

      Edit: I can see the link just fine, even without deactivating it first. Can you try clearing your browser cache?

      • neb@lemmy.caEnglish
        2·
        3 years ago

        Weird, opening in my browser now, it’s there. (And I’ve finally figured out how to make bitwarden handle sha256.) In any case, I’m all good and properly using 2FA.

    • n2burns@lemmy.caEnglish
      3·
      3 years ago

      FYI, andOTP is no longer maintained, so I’d recommend switching to an alternative and there are many options. My transition to Aegis was very smooth.

      • neb@lemmy.caEnglish
        2·
        3 years ago

        Yeah, it’s not my primary, I just happen to still have it installed.

    • durablenapkin@lemmy.caEnglish
      3·
      3 years ago

      It’s currently a little awkward, after you enable + save the first time you need to refresh the page in order to see the button which contains the otpauth:// link.

  • BeigeAgenda@lemmy.caEnglish
    1·
    3 years ago

    Just FYI I had to delete data on Jerboa before I could vote and write comments, otherwise it just logged me out again.

    • ramplay@lemmy.caEnglish
      2·
      3 years ago

      Yup just did similar excersise. Jerboa was getting confused until I unintentionally removed my old account.

      Readding then worked like a charm.