Hi,

  I backported gssproxy/0.8.2-1 (gssproxy/0.8.2-2 is not fully commited in
the git repo) and saw that this bug is still present:

Feb  4 11:01:37 ge132116vm-1 systemd[1]: Starting GSSAPI Proxy Daemon...
Feb  4 11:01:37 ge132116vm-1 gssproxy[1455]: [2021/02/04 10:01:37]: Debug 
Enabled (level: 1)
Feb  4 11:01:37 ge132116vm-1 systemd[1]: Started GSSAPI Proxy Daemon.
Feb  4 11:01:37 ge132116vm-1 gssproxy[1455]: [2021/02/04 10:01:37]: Client 
[2021/02/04 10:01:37]: (/usr/sbin/gssproxy) [2021/02/04 10:01:37]:  connected 
(fd = 10)[2021/02/04 10:01:37]:  (pid = 1456) (uid = 0) (gid = 0)
Feb  4 11:01:37 ge132116vm-1 systemd[1]: gssproxy.service: Main process exited, 
code=killed, status=11/SEGV
Feb  4 11:01:37 ge132116vm-1 kernel: [471673.673095] gssproxy[1456]: segfault 
at 0 ip 00007fc521abfe5a sp 00007ffe0a035a50 error 4 in 
libselinux.so.1[7fc521ab3000+25000]
Feb  4 11:01:37 ge132116vm-1 kernel: [471673.673103] Code: c7 45 00 16 00 00 00 
e9 df fe ff ff 0f 1f 40 00 bf 01 00 00 00 45 31 f6 e9 4c ff ff ff 0f 1f 00 41 
55 41 54 55 53 48 83 ec 08 <4c> 8b 27 49 8b 3c 24 48 85 ff 74 05 e8 95 91 ff ff 
49 8d 5c 24 08
Feb  4 11:01:37 ge132116vm-1 systemd[1]: gssproxy.service: Failed with result 
'signal'.

# apt-cache policy gssproxy
gssproxy:
  Installé : 0.8.2-1~bpo10+1


Removing the debug line in the config allows gssproxy to start.

  Regards,
    Vincent

Reply via email to