semi [he/him]

  • 1 Post
  • 30 Comments
Joined 4 years ago
cake
Cake day: September 3rd, 2021

help-circle
rss


  • I prefer KeePass over Bitwarden because it is just a simple database file, less that can go wrong (no server component).

    I am the original author of the Rust library for decrypting and modifying KeePass databases.. The current best implementation of KeePass, KeePassXC, is written in C++, so there could theoretically be security-relevant memory corruption bugs in it (though the developers of the project are excellent and I don’t think it is super likely). Rust is a language that does not have that class of issues by design, so I thought it would be interesting to see how far I could get. So far, I am still having fun and adding features bit by bit, and it is quite cool to me to be able to write one codebase that deploys to Windows, Linux, MacOS, Android (potentially iOS), and any modern web browser.

    Our son is fortunately very relaxed, he eats and sleeps a lot so I can get some coding done while he is sleeping. Germany has decent parental leave, so my partner and I are both not working the first two months of his life.




  • This is exciting. My only request here is: whenever it works please release a standalone wasm file somewhere (anywhere). So many projects either require building the wasm themselves, or instead of releasing a .wasm, they release a JS wrapper that auto-loads the wasm/wasm-imports. Its a pain to try to extract the wasm out of those projects.

    What I am doing is to create a omnikee-lib crate within the project that will get compiled to WASM, not just plain keepass, because I need additional adapter methods to interface with the web part of the application. I don’t have the bandwidth to turn keepass into a general WASM package that could be npm installed at the moment. As I am dogfooding the crate, I might get to a point where I know what a good JS interface for it would be, though, and the omnikee-lib crate could become the official WASM interface for keepass.









  • I think the Google as an identity provider example is misleading. The more common use case will be medium to small companies where several admins/developers need to login to various servers and where manually adding and revoking keys across these servers will be cumbersome.

    As the other commenter said, in those cases, the organization would also deploy its own IDP.


  • The mirrorlist is a configuration file listing servers that updates can get pulled in from.

    When a package update is installed that contains a configuration file, it will not overwrite the old file but be installed with a pacnew extension so that you can merge the files (like you did). It will keep complaining at you until you remove the pacnew file, which is fine to do after you have merged successfully.

    The graphical issues are probably due to something else that happened during the update.







  • semi [he/him]toScience Memes@mander.xyzOH SHI-
    link
    fedilink
    English
    29 months ago

    Computational protein engineer here. Pretty good explanation. I wanted to add that just because we know that a protein’s behavior changes depending on pH, it is still interesting to see what atom-level changes to the 3D structure are caused by the pH shift (e.g. so that we can better predict those changes on other proteins).