Have recently added haveged & pacman-init [daemons], both seem to start up ok. But keys are not loaded. I have to re-run pacman-key --init and pacman-key --populate archlinux post install. Have made sure pacman-init is in rc.d and haveged is running. Even added full paths to pacman-key commands without any luck. Wondering if anyone else is having the same problem?
MrG
On 09/23/2012 03:59 AM, Mr Green wrote:
Have recently added haveged & pacman-init [daemons], both seem to start up ok. But keys are not loaded. I have to re-run pacman-key --init and pacman-key --populate archlinux post install. Have made sure pacman-init is in rc.d and haveged is running. Even added full paths to pacman-key commands without any luck. Wondering if anyone else is having the same problem?
MrG
I guess you are talking about your system not archiso... so you need to patch pacman-key script, see configs/releng for such patch ;)
Mr Green mrgreen@linuxmail.org on Sun, 2012/09/23 07:59:
Have recently added haveged & pacman-init [daemons], both seem to start up ok. But keys are not loaded. I have to re-run pacman-key --init and pacman-key --populate archlinux post install. Have made sure pacman-init is in rc.d and haveged is running. Even added full paths to pacman-key commands without any luck. Wondering if anyone else is having the same problem?
Not sure when this happens to you, but I had a similar problem:
I had haveged and pacman-init run as daemon as well. However on some system the generated master key was invalid. This happens if the time is set back (by ntp client, vmware or virtualbox tools), especially if the BIOS clock is not utc.
My solution is to use libfaketime and generate the master key one day in past. This solved all my problems, see attached patch.
Do not know if this helps in your case, but it could be useful to have this included in install media.
arch-releng@lists.archlinux.org