KDE Plasma + Brave on Debian

  This is the “how do I make Brave do what I want” note --- especially when Brave profile UI is broken and KDE is strict about .desktop launchers. 1) Know what you’re running. Check where Brave comes from. which brave-browser If it returns /usr/bin/brave-browser , you’re on the APT-installed build (good, predictable). Also note that on Debian you often have both commands available. brave-browser is commonly a wrapper. brave-browser-stable is commonly the actual binary. 2) Where Brave stores its data. Default Brave user-data root (APT install). ~/.config/BraveSoftware/Brave-Browser/ If you only see Default/ , then you effectively have a single Brave “profile” in that directory. 3) Multiple isolated Brave sessions without Brave profiles. This is the clean workaround: run separate user-data directories . Create a new isolated environment. mkdir -p ~/.config/BraveSoftware/Brave-RDT Launch Brave using that directory. brave-browser-stable --user-data-dir= ...
0

Password security

Encryption 


Password encryption is ensured by the service called SHA-512 (Secure Hashing Algorithm 512 bits). It includes the protocols:

  • TLS
  • SSL
  • PHP
  • SSH
  • S/MIME
  • IPSec
SHA-512 is invoked with sha512sum. To see the encryption of the word "table":
$ echo -n table | sha512sum


Security enhancement

  • Password aging
    It sets the expiration date on a password, enabling its periodic replacement. The command to use is chage.

  • Forcing users to set strong passwords
    This can be done by using PAM - Pluggable Authentication Bodules. It is based on one of thefollowing libraries:
    • pam_cracklib.so
    • pam_passwdqc.so (provides more options


Comments

Post a Comment