(forgot to CC the mailing list earlier) > > In case we stay with openvpnserv2, I think some followup questions > need to be asked... > > - do we want to migrate "interactive service" functionality into > openvpnserv2 as well? More code, but not overly complex stuff > (if the network/route API in C# isn't totally different from C) - > and all the arguments from above apply to the interactive service > as well, of course >
Interesting question that warrants more discussion. Other implementations (NSSM, Openvpnwinserv) implement this by creating multiple services. Personally I prefer a single service managing multiple instances (in the style of IIS, Windows file sharing, etc.). Firstly, backward compatibility. Secondly, services should only be interactive when something exceptional happens. But to implement anything of that sort, the question is how we could implement interprocess communication? Do we watch registry values? Open some port? Security issues? > > - should "the service(s)" live inside the main openvpn repo, in the > GUI repo, in their own repo, ...? > Definitely main repo. But I'm not in a position to decide. > > - what code change rules apply? I tend to opt for "openvpn main repo" > rules, that is, no change goes in without review & ACK - a bad or > malicious commit to the service could compromise the system security > about as badly as a bad commit inside openvpn. I am aware that this > is a totally annoying process, especially if the code author has to > wait for months for an ACK to a trivial change - but hopefully a > somewhat larger active developer base can improve on this. > >
