So ~/.config is a hidden folder within your home directory. Open up your file browser to your home folder, then find the option to show hidden files and folders. If you don't see .config, you'll have to create it. Then navigate into it, find or create the geany folder, go into that, then find or create a folder named filedefs.
Security team of my organization told us to disable the following weak ciphers due to they issue weak keys: arcfour arcfour128 arcfour256 But I tried looking for these ciphers in ssh_config and
b) What exactly does "local" mean in this context, vs config, vs home? c) In the home directory, are there also other important common configuration directories used by multiple applications?
Whenever you run make menuconfig, make xconfig, make XXX_defconfig, make oldconfig, make localmodconfig or any of the other make XXXconfig targets in the Linux kernel source tree, this creates (if successful) a file called .config. This file is used during the compilation of the kernel and is not erased unless you erase it manually or run make mrproper. It's common to keep kernel source trees ...
After modifying the config file, I didn't see any change in the list shown when I ran ssh -Q mac. I found out that it's because ssh -Q mac lists all MAC algorithms supported by my version of SSH, not what is currently being utilized by the server. To get the list of what is currently being utilized by the server I used sshd -T | egrep '^macs'.
Here is a clean and portable version which is compatible with Bash 3 and up, on both Mac and Linux. It specifies all defaults in a separate file, to avoid the need for a huge, cluttered, duplicated "defaults" config function in all of your shell scripts. And it lets you choose between reading with or without default fallbacks: config.cfg: myvar=Hello World config.cfg.defaults: myvar=Default ...
Followed by some config of faillock that you can check in here. Use pam_unix.so to check the password of the user. [success=1] will skip the next line if the password is correct. try_first_pass to use the input of the first step. pam_faillock.so with authfail will log the failed attempt, and prevent the authen process go further with [default=die].
Starting with tmux version 3.1, ~/.config/tmux/tmux.conf works as an alternative to ~/.tmux.conf. Notice that it cannot be a hidden file in that directory.
From the sshd_config manual: The match patterns may consist of single entries or comma-separated lists and may use the wildcard and negation operators described in the PATTERNS section of ssh_config(5).
-1 Each application developer has to choose for herself where configuration files for that application are stored. Is it a per-user config? Is it a system-wide config? One can find the configuration file - it's contained in the application. strings $(type -p application) Read man strings to optimize .
