Changes since OpenSSH 9.4
This release fixes a number of bugs and adds some small features.
Potentially incompatible changes:
* ssh-keygen(1): generate Ed25519 keys by default. Ed25519 public keys are very convenient due to their small size. Ed25519 keys are specified in RFC 8709 and OpenSSH has supported them since version 6.5 (January 2014).
* sshd(8): the Subsystem directive now accurately preserves quoting of subsystem commands and arguments. This may change behaviour for exotic configurations, but the most common subsystem configuration (sftp-server) is unlikely to be affected.
New features:
* ssh(1): add keystroke timing obfuscation to the client. This attempts to hide inter-keystroke timings by sending interactive traffic at fixed intervals (default: every 20ms) when there is only a small amount of data being sent. It also sends fake “chaff” keystrokes for a random interval after the last real keystroke. These are controlled by a new ssh_config ObscureKeystrokeTiming keyword.
* ssh(1), sshd(8): Introduce a transport-level ping facility. This adds a pair of SSH transport protocol messages SSH2_MSG_PING/PONG to implement a ping capability. These messages use numbers in the “local extensions” number space and are advertised using a “ping@openssh.com” ext-info message with a string version number of “0”.
* sshd(8): allow override of Subsystem directives in sshd Match blocks.
https://www.openssh.com/releasenotes.html#9.5p1
Category: Uncategorized
-
-
Using open-source as my daily driver has increased my productivity and there is no way back to Windows in the near future. I regret not transitioning into Linux a decade ago in 2012-2013.
The next step is FreeBSD + ZFS as a desktop !! It is just the simplicity, the low maintenance, cost and complexity. Once you set your defined, prefered parameters the system can run stable for years with minimal intervention.
-
The stable version of Chomium does not allow me to sync my data across devices, while beta functions as supposed to be.
“Version 117.0.5938.149 (Official Build) Arch Linux (64-bit)” vs “Version 118.0.5993.54 (Official Build) beta (64-bit)”
UPDATE: The problem is related with the limited Private API availability and is present from March 15 2021. Unfortunately the Stackoverflow instructions were unsuccessful
https://stackoverflow.com/questions/67459316/enabling-chromium-to-sync-with-google-account
-
-
run the command:
openssl rand -base64 16
rand denotes randomness, base64 denotes readable format and 16 the password length
the output: 4twmIodX5QwjWP+OsTePLg==
-
-
- Enable Bridged Adapter
- find the ip adress of the virtual machine using the ifconfig command (in this case 192.168.0.212)
- execute ssh username@ip_adress_of_virtual_machine (in this case ssh chris@192.169.0.212, root@ip_adress does not work for safety reasons!)
-
-
Visited 452 days, 100 of which consecutive !
-
“In 2017, the kernel jumped from two years of support to six. Now, six years later, it turns out that’s a lot of work. Linux Weekly News executive editor Jonathan Corbet announced the Linux kernel will return to two years of LTS support.
The plan to cut back down to two years isn’t instant.”
According to the article the currently LTS maintained kernels are 6 🙂
-
After more than a decade of active development
-
The problem:
The solution:
sudo rm /var/lib/pacman/db.lck removes the lock of the package database that pacman created when a package is about to get altered. This mechanism prevents a different instance of pacman to perform simultaneous changes but the lock can sometimes remain stale
More about pacman troubleshooting: https://wiki.archlinux.org/title/Pacman#Troubleshooting
/root 