User talk:Sander Maijers
gpg-agent
How do you interpret the gpg-agent(1)
man page? It says
--options file Reads configuration from file instead of from the default per-user configuration file. The default configuration file is named ‘gpg-agent.conf’ and expected in the ‘.gnupg’ directory directly below the home directory of the user.
And later
gpg-agent.conf This is the standard configuration file read by gpg-agent on startup. It may contain any valid long option; the leading two dashes may not be entered and the option may not be abbreviated. This file is also read after a SIGHUP however only a few options will actually have an effect. This default name may be changed on the command line (see: [option --options]). You should backup this file.
Which IMO means that ~/.gnupg/gpg-agent.conf
is read by default, even with --daemon
. My experiments support this.
-- Lahwaacz (talk) 20:39, 14 July 2016 (UTC)
You are correct about the man page, I falsely recollected a specific detail there.
Regardless, my own practice has learned me that with --options
explicitly pointing to the default file, SSH authentication using gpg-agent
works, whereas without it, it does not. I have been testing and configuring this all afternoon, using fresh logouts, reboots and systemctl --user daemon-reload
. This may be related to the circumstance that I'm starting gpg-agent
from a systemd user unit. For example, the standard socket also isn't located in its documented place anymore. Reading e.g. [1]
- With GnuPG 2.1 the need of GPG_AGENT_INFO has been completely removed and the variable is ignored. Instead a fixed Unix domain socket named S.gpg-agent in the GnuPG home directory (by default ~/.gnupg) is used. The agent is also started on demand by all tools requiring services from the agent.
In reality, these files are only found under "${XDG_RUNTIME_DIR}/gnupg/"
when starting gpg-agent
in daemon mode under systemd as user unit.
Sander Maijers (talk) 21:01, 14 July 2016 (UTC)
- Do you have a non-default
GNUPGHOME
? Is the systemd unit exactly the same as on the wiki or can you show the customizations? - The default socket path changed in 2.1.13, see Talk:GnuPG and the note added in [2].
- Lahwaacz (talk) 21:26, 14 July 2016 (UTC)
- I haven't set
GNUPGHOME
, but perhaps the path to the GnuPG home is being normalized by GnuPG. It's a symlink in my setup. '/home/sanmai/.gnupg' -> '/home/sanmai/secrets/.gnupg'
- The systemd unit is the same as the one I've contributed to the Arch Wiki, i.e. has a single customization to the original one on the Wiki.
- Sander Maijers (talk) 14:43, 15 July 2016 (UTC)
- I haven't set
- gpg-agent seems to behave correctly for me even when
~/.gnupg
is a symlink - the config file is still loaded even without an explicit--options
parameter. -- Lahwaacz (talk) 12:44, 16 July 2016 (UTC)
- gpg-agent seems to behave correctly for me even when
- Today I had time to test again, and it works for me now without `--options`. I will correct the Wiki page now. Good catch!
- Sander Maijers (talk) 11:42, 25 July 2016 (UTC)
Windows 10 ISO
I have looked at a few ISOs and they all have the install.esd, I haven't seen the install.wim in recent versions. In which Windows 10 ISO have you seen the wim format?
Kewl (talk) 20:16, 28 November 2017 (UTC)
- Win10_1709_EnglishInternational_x64.iso
- Then both esd and wim exist in recent Windows10 ISOs, I would remove the explicit reference to Windows 10 in the wiki
- Why do you believe install.esd exists? It doesn't in that ISO. If you have evidence this is true for more ISOs, feel free to specify that.
- There are ISOs using wim and esd format: it depends how they are created, esd is the new format achieving better compression but is less friendly for deployment across networks using older windows versions Kewl (talk) 11:14, 29 November 2017 (UTC)