• 0 Posts
  • 40 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle
  • password managers in the browser still store them encrypted. They usually authenticate via a passkey, in-built security in the OS like windows hello, or through other services such as SSO through google; That said, if you have them on auto-pilot with this authentication, anyone with access to the device can theoretically access them, though to actually view them in the password manager they usually require you to authenticate.

    Browser password managers are sorta less secure than a third party one, assuming you turn on all the convenience features to make your life easier, but a lot of third-party password managers have the same convenience features a lot of the time anyways.


  • Saving the password in your browser is using a password manager; you’re just using the one built into your browser. The safety and security of using any individual password manager is pretty much up to how secure that particular password manager is, but generally speaking they all store passwords encrypted.

    Ones built into a browser have the added attack vector of being potentially vulnerable from the browser itself vs a stand alone manager, but if you use a plugin for your favorite password manager they likely share a pretty similar attack vector possibility.

    Either way, using a password manager is infinitely better than reusing passwords, so this is really just a long winded way of saying “no, not really”.

    Dedicated password managers usually come with more security, control, and features, but you’re generally going to be fine using the one built into your browser.





  • i second the comment that you need to consider why you want to do this. You generally need a pretty good reason to split your codebase into multiple languages.

    As far as actually doing it, you have a ton of different options, some of which have been mentioned here. Some i can think of off the top of my head:

    • create a library (dll or so file or the like)
    • set up a web server and use communication protocols (either web socket or rest API or the like)
    • use a 3rd party communication/messaging framework like MQ or kafka or something
    • create your own method of communication. Something like reading and writing to a file on disk, or a database and acting on the information plopped in

    basically every approach is going to require you to come up with some sort of API that the two work together through, though, an API in the generic sense is basically a shared contract two disconnected pieces of code use to communicate.