spangey/raw gpg note snips

## raw gpg note snips
-s2k-mode n

Selects how passphrases are mangled. If n is 0 a plain passphrase (which is not recommended) will be used, a 1 adds a salt to the passphrase and a 3 (the default) iterates the whole process a number of times (see –s2k-count). Unless --rfc1991 is used, this mode is also used for conventional encryption.

--s2k-count n

Specify how many times the passphrase mangling is repeated. This value may range between 1024 and 65011712 inclusive. The default is inquired from gpg-agent. Note that not all values in the 1024-65011712 range are legal and if an illegal value is selected, GnuPG will round up to the nearest legal value. This option is only meaningful if --s2k-mode is 3.

This explains it quite well in my opinion. By default s2k-mode is set to the 'most secure' method available. With s2k-count you can increase the amount of times your password gets mangled. Honnestly I would just leave it by default for the sake of compatibility. Considering the algorithms you are using (AES-256) you should be quite secure as long as you use a strong password.
	-s2k-mode n

	Selects how passphrases are mangled. If n is 0 a plain passphrase (which is not recommended) will be used, a 1 adds a salt to the passphrase and a 3 (the default) iterates the whole process a number of times (see –s2k-count). Unless --rfc1991 is used, this mode is also used for conventional encryption.

	--s2k-count n

	Specify how many times the passphrase mangling is repeated. This value may range between 1024 and 65011712 inclusive. The default is inquired from gpg-agent. Note that not all values in the 1024-65011712 range are legal and if an illegal value is selected, GnuPG will round up to the nearest legal value. This option is only meaningful if --s2k-mode is 3.

	This explains it quite well in my opinion. By default s2k-mode is set to the 'most secure' method available. With s2k-count you can increase the amount of times your password gets mangled. Honnestly I would just leave it by default for the sake of compatibility. Considering the algorithms you are using (AES-256) you should be quite secure as long as you use a strong password.