• unskilled5117@feddit.org
    link
    fedilink
    English
    arrow-up
    207
    arrow-down
    2
    ·
    edit-2
    17 days ago

    This is an important issue IMO that needs to be addressed and the official response by Bitwardens CTO fails to do so.

    There is not even a reason provided why such a proprietary license is deemed necessary for the SDK. Furthermore this wasn’t proactively communicated but noticed by users. The locking of the Github Issue indicates that discussion isn’t desired and further communication is not to be expected.

    It is a step in the wrong direction after having accepted Venture Capital funding, which already put Bitwardens opensource future in doubt for many users.

    This is another step in the wrong direction for a company that proudly uses the opensource slogan.

    • sunzu2@thebrainbin.org
      link
      fedilink
      arrow-up
      66
      arrow-down
      4
      ·
      17 days ago

      Welp, I guess another time to move here soon.

      And I just fucking vouched for them to a friend recently 🤡

      Didn’t know about VC funding these parasites using their funding to turn everything into shite.

      What’s the current “best” alternative? Keepass?

      • foggenbooty@lemmy.world
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        1
        ·
        17 days ago

        I haven’t jumped yet, but the Proton suite is looking more and more appealing. I’ve been eyeing them as a Gmail replacement, but I’ve been happy with my VPN and password management providers. As this reduces the bundle makes more sense.

        • sunzu2@thebrainbin.org
          link
          fedilink
          arrow-up
          30
          arrow-down
          2
          ·
          17 days ago

          They have a solid value proposition but don’t like putting all my eggs all in one basket both for security and monopoly reasons.

          They seem to be gunning for one stop shop and I think they are doing decent shop but I just don’t like the idea after what Google did to us.

          Situation is a bit different but gonna need to tka the lessons and not let these corpos do this again.

          • foggenbooty@lemmy.world
            link
            fedilink
            English
            arrow-up
            6
            ·
            17 days ago

            That’s a good practice, and I think you’re right that is what they’re going for. I don’t think that means you shouldn’t consider them, but it does lower their value proposition as the bundle is the better deal.

          • Caboose12000@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            16 days ago

            this isnt a full solution obviously, but I figured it’d be nice to know: Proton lets you set different passwords for your email and password manager, so at least from a security standpoint its not all behind the same password, even if it is still from the same company

      • Artaca@lemdro.id
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        16 days ago

        It’s not open source, but I got a lifetime license for Enpass over a decade ago and it’s done everything I’ve ever needed it for. I think stacksocial occasionally has new lifetime codes for sale. I like the idea of Proton Pass as others have said, but it feels a bit like putting all my eggs in one basket, which is a mistake I already made with Google before (context: I use Proton for email). I think Keepass is the next best option if dedicated to staying FOSS.

    • irotsoma@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      16 days ago

      They’re basically trying to get rid of vaultwarden and other open source forks. I expect they’ll get a cease and desist and be removed from github at some point in the not too distant future if they don’t make some changes. I have a vaultwarden instance and use the bit warden clients. Guess I’ll need to look for alternatives in case Bitwarden decides to get aggressive.

  • ShittyBeatlesFCPres@lemmy.world
    link
    fedilink
    English
    arrow-up
    130
    arrow-down
    3
    ·
    17 days ago

    Oh, for fuck’s sake. Can we have a decent password manager that isn’t tied to a browser or company? I pay for Bitwarden. I’m not being cheap. But open source is more secure. We can look at the code ourselves if there’s a concern.

      • sigmaklimgrindset@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        27
        ·
        16 days ago

        Love Keepass. Love that I can sync it however I want. Love that there are multiple open source client options across several operating systems.

        • saddlebag@lemmy.world
          link
          fedilink
          English
          arrow-up
          29
          arrow-down
          1
          ·
          16 days ago

          Android syncthing announced they’re stopping development this year. Open source got fucked double today

        • Bilb!@lem.monster
          link
          fedilink
          English
          arrow-up
          3
          ·
          16 days ago

          This need not be the case, though! There’s an open source client on Android called Keyguard. I don’t think the desktop app was at all useful anyway. You can just log into your Vaultwarden through any browser. The desktop app is pointless.

          • pmc@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            21
            ·
            16 days ago

            They now require a non-free Bitwarden SDK component. That’s what this whole conversation is about.

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              2
              ·
              16 days ago

              And the whole conversation is about a bug, not a change in direction…

              Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

            • fmstrat@lemmy.nowsci.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              16 days ago

              Only the desktop client. And the response is that not being able to compile sans SDK is an issue they will resolve.

              I still think this is bad directionally, but we need to see what happens.

    • asap@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      edit-2
      16 days ago

      Nothing in the article or in the Bitwarden repo suggests that it’s moving away from open source

      • coolmojo@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        16 days ago

        It is a license problem. The license condition of the SDK which is required to build the client app change to limit the usage of it. The new license states that you can only use the Bitwarden SDK for Bitwarden. It is against the Freedoom-0 of the Free Software Foundation. The limitation of English language is that it is hard to differentiate between Free (as in Free bear) and Free (as in Freedoom). Also open source which could mean complaining with FOSS and that source is available. This been unfortunately have been abused before.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          16 days ago

          From the article, it’s a packaging bug, not a change in direction.

          Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              5
              ·
              16 days ago

              Here is the code in question. Basically, it’s a source-available, but not FOSS internal SDK, with the following language:

              The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.

              So I think the “bug” here is in not linking the original repo in the NPM package, and there’s a decent chance that this internal SDK will become FOSS in the future once it stabilizes. That said, it’s currently not FOSS, but it’s too early IMO to determine whether Bitwarden is moving in a non-FOSS direction, or if they’re just trying to keep things simple while they do some heavy refactoring to remove redundancy across apps.

              Given their past, I’m willing to give them the benefit of the doubt, but I’ll be making sure I have regular backups in case things change.

  • cmrn@lemmy.world
    link
    fedilink
    English
    arrow-up
    111
    arrow-down
    2
    ·
    edit-2
    16 days ago

    EDIT: The article has been updated and it was described as a “packaging bug” and not an intended change.

    How many times do I need to pack up and move to the next “best option”

    • JustARaccoon@lemmy.world
      link
      fedilink
      English
      arrow-up
      49
      ·
      17 days ago

      Sadly as many times as needed, complacency is how these companies get “loyal customers” who are willing to put up with bs

      • doktormerlin@feddit.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        16 days ago

        That’s far from the best option. It’s working, but it’s super complicated compared to Bitwarden and other cloud password managers. Imagine telling your grandma “just use keepass”, she would never be able to make it work. But Bitwarden? Lastpass? That’s possible

        • cy_narrator@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          14 days ago

          Is it so?

          I feel like anyone who can open up and edit ms word can do it, just double click on the keepass.kdbx file and it opens up prompting for a password.

          Syncing is a bit of a problem and I wrote an article on how I do it here in the easiest way I found. Though MEGA cloud does not have a good reputation among general public, their share link is something you can write in a piece of paper and keep in a safe.

          • doktormerlin@feddit.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            13 days ago

            “Just double click the keepass.kdbx” is not what it is. You need to go to your explorer, find the file in the folder structure and double click it. You then need to search for the website you are on and copy the password, then you need to go back to the website within 12 seconds and paste the password. That’s inconvenient for everyone, but for a tech-illiterate grandma it’s impossible.

            Compare that to Bitwarden: You go to the website, click on the bitwarden icon and then click on the login details. Or even better, you can enable auto-complete with a single click and it automatically fills the login details when on the website, without clicking anything. That’s far more convenient and easier.

            Just as a FYI: My grandma has a sticky note on her laptop that shows exactly which buttons to press to get to her emails, with things like “Click this twice within 2 second, be fast!!” for a double click. It doesn’t say “lef mouse button”, she draw her touchpad and an arrow. She is not able to find her mails when the website changes the layout.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      16 days ago

      In this case, zero, because it’s a packaging bug, not an actual change in direction. Read the update on the article:

      Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

      Next time, before jumping to conclusions, wait a day or two and see if the project says something.

      • 486@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 days ago

        I really hope that this is actually the case, but I am not very optimistic. This doesn’t seem to be a mistake. They intentionally move functionality of their clients to their proprietary SDK library. The Bitwarden person stated this in the Github issue and you can also check the commit history. Making that library a build-time dependency might actually have been a mistake. That does not change the fact, that the clients are no longer useful without that proprietary library going forward. Core functionality has been move to that lib. I really don’t care if they talk to that library via some protocol or have it linked at build time. I wouldn’t consider this open source, even if that client wrapper that talks to that library technically is still licensed under GPLv3.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          16 days ago

          They intentionally move functionality of their clients to their proprietary SDK library.

          Proprietary is a strong word IMO. Here’s the repo, it’s not FOSS, but it is source available. It’s entirely possible they make it more open once it stabilizes, but it’s also possible they make it less open as well. It’s still early, so we don’t know what the longer term plans look like.

          I don’t think we should be panicking just yet, but I’ll certainly be checking back to see what happens once this internal refactor is finished, and I’ll be making some more regular backups just in case they are, in fact, trying to take it proprietary. I don’t think that’s the case (why would they? I don’t see the benefit here…), but I guess we’ll see.

          • 486@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            16 days ago

            Proprietary is a strong word IMO. Here’s the repo, it’s not FOSS, but it is source available.

            Yeah, that’s what I meant by “proprietary”. I guess having the source to look at is better than nothing, but it still leaves me uneasy. Their license lets them do anything they want (ignoring that - as it stands - their license is void due to the linkage with GPLv3 code, but they said they want to fix that). I have no idea what their plan is. I don’t think it is in their best interest to go the route they appear to be going. Having truly open source clients seems to be a selling point for quite a few customers. But what do I know…

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              16 days ago

              Agreed. If they end up not making this component FOSS, I’ll probably leave and take my paltry $10/year with me (which I don’t need to pay since the features I use are all in the free version). But I’ll give them a year or so to work out whatever refactoring they’re doing before making that call, I’m certainly not going to jump ship just because a new component is merely source-available.

  • ayyy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    82
    arrow-down
    12
    ·
    edit-2
    16 days ago

    600 upvotes and only 10 downvotes on literal fake news. I wish readers were less lazy, it’s very frustrating.

    Edit: made my statement a bit less toxic. I was mad.

    • ammonium@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      ·
      16 days ago

      How is it fake news? They are moving functionality into a proprietary SDK and have a whole framework ready to get around the GPL.

    • octopus_ink@lemmy.ml
      link
      fedilink
      English
      arrow-up
      8
      ·
      16 days ago

      No one is listening I’m sorry to say. I corrected a couple people but then realized it was pointless. The discussions in the crossposted communities (which - holy shit I don’t think I’ve seen something so thoroughly spammed across multiple tech communities before) are just as bad or worse.

    • locuester@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      16 days ago

      Community is fine, your comment is at the top, along with others pointing this out.

      It’s the “non-community” if you will boosting this. The passerby’s not reading comments.

    • qaz@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 days ago

      Why would it be fake news? Because they called it a “packaging bug”?

        • qaz@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          15 days ago

          To me that just like an excuse for the current mess. Did you read the original GitHub issue? Their CTO also seems to have questionable ideas about the GPLv3.

  • Boozilla@lemmy.world
    link
    fedilink
    English
    arrow-up
    58
    ·
    17 days ago

    Goddammit. It’s getting to the point I’m going to have to figure out how to write my own app for this.

    • Humanius@lemmy.world
      link
      fedilink
      English
      arrow-up
      20
      arrow-down
      17
      ·
      edit-2
      17 days ago

      It shouldn’t even be that complex…

      I might be mistaken, but ultimately a password manager is basically nothing more than a database of passwords in an encrypted zip file, right? That could entirely be self-hosted with off the shelf open source applications stringed together.
      All you’d need is a nice UI stringing it all together.

      Edit: I’m not sure why people are downvoting me. Is that not what a password manager essentially is?

      • wintermute@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        30
        ·
        17 days ago

        Keepass is exactly that. Basically all the client side parts, and the database is a single encrypted file that you can sync however you want.

      • LedgeDrop@lemm.ee
        link
        fedilink
        English
        arrow-up
        9
        ·
        16 days ago

        It’s the “stringing it all together” that could be problematic.

        If you have multiple clients (desktop/cellphone) modifying the same entry (or even different entries in the same “database” ). You need something smart enough to gracefully handle this or atleast tell you about it.

        I did the whole “syncing” KeePass and it was functional, but it also meant I needed to handle conflicts - which was annoying. I switched and really appreciate the whole “it just works” with self-hosted bitwarden.

      • xthexder@l.sw0.com
        link
        fedilink
        English
        arrow-up
        9
        ·
        17 days ago

        I’ve done basically this in the past by encrypting a text file with GPG. But a real password manager will integrate with your browser and helps prevent getting phished by verifying the domain before entering a password. It also syncs across all my devices, which my GPG file only worked well on my desktop.

      • HereIAm@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        17 days ago

        I see it as it’s easy to self host. But I’m not skilled nor rich enough to guarantee the availability of it. I don’t want to be stuck on a holiday without my passwords because my server back home died from black out or what have you.

        I pay for bitwarden and the proton mail package to keep the password management market a bit more competitive and it actually works out cheaper. It would be nice to have protons anonymous emails built in, but I can live with it.

        But I might have to reconsider if Bitwarden is going a different direction that what I’m paying for.

      • Boozilla@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        16 days ago

        Thank you for the update! I would like to keep using it. I’ve been very happy with Bitwarden both as a password manager and a TOTP authenticator. I have even recommended it to my boss as an enterprise solution for us to use at work, and so far we are planning on replacing our current password database solution with Bitwarden.

        Unfortunately, with “enshittification” being so common these days, it was very easy to believe they were also going to the dark side. I will remain cautiously optimistic after learning it was a packaging bug.

        Here’s a link to the post on X (yes, I hate X, too) in case anyone else is doubtful:

        https://x.com/Bitwarden/status/1848135725663076446

        • ArxCyberwolf@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          16 days ago

          Yeah, I was worried about it too. I’ve become pretty cynical when it comes to everything becoming enshittified, but I’m hoping they stick to their word.

      • NanoooK@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        15 days ago

        That’s what I’m using mostly, but the convenience of having auto fill in firefox and being able to share some logins made me want to try bitwarden. Also, it’s not complicated to sync between several devices.

  • mli@lemm.ee
    link
    fedilink
    English
    arrow-up
    38
    ·
    16 days ago

    Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

    According to Bitwardens post here, this is a “packaging bug” and will be resolved.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      16 days ago

      Honestly, if he can replace the current Bitwarden BE w/ Vaultwarden, that would be awesome! The last time I looked at the Bitwarden self-hostable BE, it was super heavy, which is the entire reason I was interested in Vaultwarden.

      • Magnus Åhall@lemmy.ahall.se
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 days ago

        I’m running a couple of Vaultwarden instances, and it would be really nice if Bitwarden employed Garcia to improve the Rust backend. But as the bitter cynic I am, I guess it is an effort to shut down and control as much of the open source use of Bitwarden as possible.

        The worst case, someone will most likely fork Vaultwarden and we can still access it with Keyguard on mobile and the excellent Vaultwarden web interface :)

        • Magnus Åhall@lemmy.ahall.se
          link
          fedilink
          English
          arrow-up
          2
          ·
          16 days ago

          Phew, looks good on the news with the packaging bug (if they didn’t just got cold feet for worse PR/backlash than they expected and this is a backtracking).

          In this case, hopefully Garcia is employed for his expertise and can be deployed to further open source relations :)

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          16 days ago

          And I am an ardent optimist, hence why I see it as a good thing.

          But yes, worst case someone will fork it, and I’ll probably use that fork.

    • Routhinator@startrek.website
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      16 days ago

      I’ve always loved Keepass, however I moved away from it in 2012 as it and any file based vault has brute forcing issues. You need to track every copy of it that has been made and if any copy falls out of your hands, like if you lose a device, you need to do a password rotation on 100% of your passwords. Since its a file, its not possible to prevent brute forcing.

      • ocassionallyaduck@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        13 days ago

        An online database is still a file ultimately. A SQL or other DB file stored in a webserver, accessed through a web interface.

        Vaultwarden, etc, are the same, only the database file is less directly visible IMO. Keepass IMO is simple. The DB in a bespoke format, stored outside the application.

        You could put the vault in system32 and name it “trustedinstaller.log”, and if someone saw you had keepass they wouldn’t even know where your vault is.

        Given the number of well documented breaches of online password vaults, I would much rather do a private device to device sync via syncthing and keep it out of webservers.

      • solsangraal@lemmy.zip
        link
        fedilink
        English
        arrow-up
        6
        ·
        17 days ago

        so the “no longer open source” means they’ll be moving to a saas model or something? i’m not super cybersecurity savvy but bitwarden is what i use

        • winterayars@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          71
          ·
          17 days ago

          No, technically they already are SaaS company. That’s mostly how they make their money.

          Also it should be noted “no longer open source” doesn’t mean they’ve done a “our code is now closed and all your passwords are ours” rug pull like some other corporations. This is a technical concern with the license and it no longer meets proper FOSS standards (in other words, it has a restriction on it now that you wouldn’t see in, for example, the GPL).

          So by and large the change is very minimal, the code is still available, it’s still the best option. However, this does matter. It may be a sign of the company changing directions. It’s something they should get pushback about.

          • dustyData@lemmy.world
            link
            fedilink
            English
            arrow-up
            11
            arrow-down
            1
            ·
            edit-2
            17 days ago

            The SDK was never FOSS, and was never under the GPL. Hence why they can add the text mentioned in the article. You don’t get to change the text of a FOSS license to begin with. It isn’t unheard of for text like this to be part of proprietary software that integrates with and uses FOSS that are under different licenses.

            That said, this is concerning, but whether it changes BW’s FOSS state is a matter of legal bickering that has been going on for decades.

          • sugar_in_your_tea@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            16 days ago

            From the update, it looks like they consider it a bug, which they’re working to resolve. Let’s see how they resolve it before jumping to conclusions.

      • ilmagico@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        arrow-down
        1
        ·
        17 days ago

        +1 For KeePassXC and the KeePass ecosystem. Yes, you need to sync the database yourself, but you can use any file sharing service you like, e.g. google drive, dropbox… or selfhost something like nextcloud (like I do), which for me is actually a point in its favor.

        Based on this news, I think I made the right choice back then when I decided to go with KeePass.

        • kill_dash_nine@lemm.ee
          link
          fedilink
          English
          arrow-up
          6
          ·
          17 days ago

          As someone who used to use KeePass, went to LastPass, and then Bitwarden (Vaultwarden), I finally got my non-tech literate wife to use Bitwarden. I’m concerned that KeePass might end up being more difficult if it comes down to it. I believe that KeePass had some sort of browser integration but it really has been a long time since I used it so who knows the current state. Curious how browser integration is today.

          • GHiLA@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            4
            ·
            edit-2
            16 days ago

            The big issue isn’t using it, it’s syncing it.

            User A used KeePass to order pizza and changed the Papa John’s(heaven forbid) password while they were at it, on their desktop.

            syncing: “oh! This file changed! Neat!”

            User B picks up their phone and wants to order Papa John’s at work. They try, but the password isn’t right. Huh. They check KeePass. No issues. They go to change the password because they think something is wrong.

            (All the while, they never thought to see if syncthing had been woken up in the background lately)

            They change the password, update KeePass,

            syncthing opens later, goes: "Oh, hi, User B’s phone! I have a ne- Oh! You have a new password file too!!? Small world! I’ll take both!

            Now there’s two files, two users who think they both made corrections to a password, syncthing thinking nothing is wrong, and someone has to now merge the newer KeePass file over the old ones by hand and realize what happened, but the bigger problem is, no one knows anything is wrong yet and it doesn’t even take two users. This can just be you ordering on your phone after modifying on your desktop.

            well, it’s just pizza.

            As an example. Imagine an insurance app, or a banking app, or the DMV… And you won’t know for months down the line. It gets old.

            • kill_dash_nine@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              16 days ago

              Ah yeah, the fun of how that works. I recall that I had previously set up WebDAV to try to simplify my source of truth but I think that was just with the original KeePass app, not KeePassXC. I also wasn’t trying to share passwords among multiple people but I do recall having issues when I was using Dropbox to sync to my phone since I would have to actually make sure Dropbox had updated the copy of the file which required me opening the app at the time.

            • ilmagico@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              16 days ago

              I use KeePassXC on desktop and Keepass2Android on, well, android, and sync via nextcloud. They all seem to handle syncing correctly, merging changes made on one side, or showing a notification about a conflict, and KeePassXC can definitely merge the two “conflicted copies” together reliably with a couple of clicks (yes, a no-click solution would be better, I know, but it’s not “manual”). Keepass2Android integrates directly with nextcloud and seems to handle it fine.

              The situation can definitely be improved but it’s not so bad for me. Also, two different people should probably use two different database files and not share passwords ;)

              Not sure how syncthing handles conflicts, it’s been many years since I tried it.

          • ilmagico@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            16 days ago

            I use KeePassXC’s browser integration daily and it works pretty well with Firefox (linux), well enough that I’m not complaining, but I cannot compare it with Bitwarden cause I never used it. On Android I use Keepass2Android and works well with autofill, but again, I can’t really compare it.

            Something tells me Bitwarden works better, just by virtue of being a commercially supported product, but I have no complaints with KeePassXC & Keepass2Android (KeePassDX works well on android too). Original KeePass desktop client was never great though.

    • oaklandnative@lemmy.world
      link
      fedilink
      English
      arrow-up
      21
      ·
      17 days ago

      Proton Pass is open source and the company that runs it recently reincorporated as a Swiss non-profit to ensure their privacy mission can’t be bought out by venture capitalists etc.

      https://www.reddit.com/r/ProtonPass/comments/153t85q/proton_pass_is_open_source_and_has_now_passed_an/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

      https://proton.me/blog/proton-non-profit-foundation

    • ChillPill@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      17 days ago

      Keepass? No cross device support, you need to manage that yourself through something like Google Drive…

      • ilmagico@lemmy.world
        link
        fedilink
        English
        arrow-up
        20
        arrow-down
        4
        ·
        17 days ago

        What do you mean “no cross device support”? KeePassXC supports Win, Mac, Linux and there are iOS and Android apps available…

        As for the lack of cloud and requirement to provide your own synchronization, for some (like me) that’s a feature, not a limitation :)

        • hedgehog@ttrpg.network
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          17 days ago

          Do any of the iOS or Android apps support passkeys? I looked into this a couple days ago and didn’t find any that did. (KeePassXC does.)

          • ilmagico@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            17 days ago

            I don’t use passkeys so I don’t know. Maybe I should research into passkeys, what’s the benefit over plain old (long, randomly generated) passwords?

            • jqubed@lemmy.world
              link
              fedilink
              English
              arrow-up
              5
              ·
              17 days ago

              I’m no expert in this but the passkeys really on some sort of public key, cryptographic pair. Your device will only send your encrypted cryptographic secret when it gets the correct encrypted cryptographic secret from the destination. This makes it much harder to steal credentials with a fake website or other service.

            • ilmagico@lemmy.world
              link
              fedilink
              English
              arrow-up
              4
              arrow-down
              4
              ·
              edit-2
              17 days ago

              Ok, from a quick search, it seems passkeys rely on some trusted entity (your browser, OS, …) to authenticate you, so, yeah, I’m not sure if I like that. The FIDO alliance website is all about how easy, convenient and secure passkeys are, and nothing about how they actually work under the hood, which is another red flag for me.

              I’ll stick to old-fashioned, long, secure, randomly generated passwords, thanks.

              • deejay4am@lemmy.world
                link
                fedilink
                English
                arrow-up
                4
                ·
                17 days ago

                Passkeys rely on you holding a private key. The initial design was that a device (like a browser or computer/phone) stored the private key in a TPM-protected manner, but you can also store it in a password manager.

                This is more secure than a password because of the way private/public key encryption works. Your device receives a challenge encrypted with the public key, decrypts with the private key and then responds. The private key is never revealed, so if attackers get the public key they can’t do shit with it.

                Just be sure that your private key is safe (use a strong master password for your PM vault) and your passkey can’t be stolen by hacking of a website.

                • ilmagico@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  3
                  arrow-down
                  1
                  ·
                  17 days ago

                  I see, that makes sense and should be more secure, in theory. Thanks for the explanation.

                  The issue I have is, whether I need to trust a third party with my private key, e.g. Google with Android, Microsoft with Windows, etc. (yes on linux it’s different, but that’s not my only OS).

                  Also if the private key does get compromised (e.g. local malware steals it), hopefully there’s an easy way to revoke it.

              • ilmagico@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                16 days ago

                I was finally able to find some technical detail on passkeys on FIDO website, and yeah, it actually looks like it’s a real improvement over passwords: it’s simple, uses proven technology (public/private keys), and should be much more secure than passwords.

                Also, nothing in the “specs” says I need to entrust my private key with the OS or a third party, which is good.

                That said, it seems some OS support is required nonetheless, to show the pin / biometrics prompt (or is it?), and on android at least, I’d need to buy a new device with Android 14 to use a non-Google passkey provider…

      • solsangraal@lemmy.zip
        link
        fedilink
        English
        arrow-up
        6
        ·
        17 days ago

        lol that’s what i used before i switched to bitwarden-- didn’t have any complaints, but the database key file thing was kind of a pain

  • ealoe@ani.social
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    5
    ·
    16 days ago

    Some guy at bitwarden clicks a button wrong on a license drop-down option and all these people crawl out of the woodwork to declare the end of bitwarden being trustworthy. Nothing in the article or the company’s statements indicates an actual move away from open source. Big nothingburger

    • 486@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      16 days ago

      Maybe you want to read the comment by kspearrin in that Github issue again. They are clearly moving away from open source. He explicitly states that they are in the process of moving more code to their proprietary “SDK” library.