bin/53592: racoon is confused about adminsock

[Hauke Fath <hf%spg.tu-darmstadt.de@localhost>]

>Number:         53592
>Category:       bin
>Synopsis:       racoon is confused about adminsock
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 11 12:25:00 +0000 2018
>Originator:     Hauke Fath
>Release:        NetBSD 8.0_STABLE
>Organization:
Technische Universitaet Darmstadt
>Environment:
	
	
System: NetBSD Anscharte.nt.e-technik.tu-darmstadt.de 8.0_STABLE NetBSD 8.0_STABLE (HP2170P) #0: Fri Aug 3 14:36:04 CEST 2018 hauke%Anscharte.nt.e-technik.tu-darmstadt.de@localhost:/var/obj/netbsd-builds/8/amd64/sys/arch/amd64/compile/HP2170P amd64
Architecture: x86_64
Machine: amd64
>Description:

	The racoon roadwarrior client setup in
	/usr/share/examples/racoon/roadwarrior/client sets the
	location and permissions of a control socket in a "listen { }"
	section. With adminsock not set, the socket will be in
	/var/run per default.

	When you set adminsock, you will find the socket is
	not where you set it to; instead, you will find that
	/etc/racoon/phase1-down.sh is a socket, with permissions and
	ownership as specified for adminsock, and racoonctl will fail
	with an obtuse error.

	
>How-To-Repeat:

	Set up racoon with the roadwarrior client sample configuration.

	
>Fix:

	Sure, why not?
	

>Unformatted: