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

Transferring files: FTP, SSH, SCP

FTP

FTF is the oldest protocol. Still used, but deprecated if we speak about security as passwords are not encrypted. Nowadays replaced by:

  • rsyc
  • sftp which is via ssh
  • ncftp
  • yafc
  • ncftp
  • yafc

Secure Shell - SSH

SSH is a cryptographic protocol for secure data transmission.

$ ssh <system_machine>
Logs in to the destination system machine

$ ssh -l <someone> <system_machine>
or
$ ssh <someone@system_machine>
Logs in to the destination system machine with the specified user credentials


SCP

$ scp <localfile> <user@remotesystem>:/home/user/
Copies files between two secure networked hosts via SSH. The transfer is protected by password, which is related to the transfer itself instead of the destination machine.


Comments

Post a Comment