Your friendly neighbourhood sh.it.head

A Reddit refugee after 8 years of Reddit-ing

  • 1 Post
  • 6 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • For iOS devices the most up to date client is “Strongbox”. I don’t think it is FOSS, but is compliant with the standard. It’s sadly a freemium app, but is quite well made in my testing. It cannot sync with syncthing, but does support several cloud services, its own service (which uses iCloud), and local file transfer over LAN. They also have a version of the app with all network connectivity removed for security (if you prefer)


  • This is perhaps overkill, but you can also encrypt the contents of your online cloud storage with CryFS / Cryptomater. This is particularly useful if you wish to store sensitive documents (healthcare, finances etc) in a cloud environment in case of catastrophic destruction of property (destroying computers / on site backups of data).

    In this case you can also backup your keepass file in this encrypted virtual storage medium, on top of the prexisting encryption of the database itself.


  • Whooping_Seal@sh.itjust.workstoAsklemmy@lemmy.mlPassword Managers
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    5 days ago

    My personal choice right now is KeePassXC (PC) / KeePassDX (Android) + Syncthing And Aegis (Android) for 2FA codes, with a yubikey for services that support FIDO keys.

    Overall I like this setup because it’s decentralized and does not rely on a third party server structure. The only “weak” point would be the Syncthing relay servers or the Tailscale VPN that I use, but this goes back to ensuring encryption of the database is adequate with a long password, and using an open source synchronization protocol that ideally has been vetted by a trusted third party (or yourself if you’re capable)

    I used to use Bitwarden, and I highly recommend it. I really appreciated it’s ability to integrate with email aliasing solutions to generate new aliases from within the bitwarden UI itself. However, my main reasons for switching were the following

    • I don’t have the money to pay for it (uni student)
    • I prefer a more self-hosted approach (I will consider using vaultwarden in the future when I have more money)
    • I wanted to move away from using a browser extension for password management on desktop. KeePass’ auto type feature is really good, and a more secure input method than a browser extension autofill.

    The only additional advice I have for both recommendations is that I do not think it advisable to add Totp 2fa information to your password manager even if it supports it. I feel like this should be separate, on a single device, and backed up in ~2 locations (one preferably off site). This is really to avoid problems if a device is compromised and if your password manager is compromised, but this is definitely in the more unlikely category I feel.

    My only major issues with keepass are the potential for sync conflicts and the some feature differences between platforms. A centralized server config like vault/bitwarden prevents the sync conflict issues, at the cost of having one point of failure. The feature differences problem isn’t too great, but autotype doesn’t work on Linux if you install with flatpak, and you can’t prevent screen capture of the app on Linux (only on Android and Windows from my understanding)

    Edit: I also tried gopass, it’s really fun to have an entire CLI based password manager, but frankly the state of mobile companion apps are appalling. The Android option only is good if you use a dev version, and the iOS one I thought was just ok. I also dislike the metadata leaking that is inherent to the format, and that PGP is the main form of encryption for the time being (some clients were looking at using AGE at some point). Overall it’s a cool but flawed concept, and I feel my other two recommendations are superior.



  • The plugin that brings the “starter” / “welcome” screen when nvim is called without a file is mini.starter, a lua module of the mini plugin. My primary use case for neovim is closer to a feature complete text editor rather than a full fledged IDE, although there definitely is some overlap in my setup.

    My set of plugins are roughly as follows

    • vim-plug, I will likely replace this one with packer at some point
    • goyo.vim and limelight.vim for distraction free viewing and editing
    • nnn.nvim to integrate the nnn file manager into neovim
    • mini.nvim according to the Github, “Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort. They all share same configuration approaches and general design principles.”
      • mini.surround feature rich surround actions
      • mini.statusline a very simple no-frills statusline
      • mini.starter aformentioned start screen
      • mini.pairs inserts the paired character, e.g typing ( will automatically place ) behind the cursors
      • mini.move move selections
      • mini.map has a little map of the file similar to VScode among many other IDEs & text editors
    • barbar.nvim Tabbar plugin
    • a whole bunch of LSP / autocomplete engines / snippets / git commit messages & signs
    • nvim-treesitter for syntax highlighting

    And the remaining things in my init.lua file are just keybindings, setting up the plugins, and disabling the swapfile etc. when editing my password secrets in gopass among other ‘secret’ files


  • It definitely is rather reminiscent of older Windows versions with the seperate application launchers, fully expanded task bar entries that show the name of an app that are ungrouped (until necessary). And the widgets are very reminiscent of Rainmeter.

    But I also bring some things from macOS that I enjoyed such as the global menu on the top (sadly Firefox flatpak does not support), virtual desktops with the pager widget on the bottom, and I use Krunner a lot (plasma’s equivalent to macOS “Spotlight”)

    I hope your switch to Linux goes well if / when you switch!