[Openvpn-devel] [Patch] revoke scripts were broken

2004-06-29 Thread Jan Kiszka
Hi all, here is a tiny patch to make revoke-crt and make-crl work seamlessly within the easy-rsa environment. Seems that no one used it before ;) Jan PS: Has anyone ever thought about some small GUI (taskbar icon with some dialogs) for Windows, KDE, etc. to make the handling of multiple co

Re: [Openvpn-devel] [Patch] revoke scripts were broken

2004-06-30 Thread Jan Kiszka
Mathias Sundman wrote: On Tue, 29 Jun 2004, Jan Kiszka wrote: PS: Has anyone ever thought about some small GUI (taskbar icon with some dialogs) for Windows, KDE, etc. to make the handling of multiple configurations and the status display easier in a roadwarrior scenario? Just a thought, I&#

Re: Interface with GUI agent, was: Re: [Openvpn-devel] [Patch] revoke scripts were broken

2004-06-30 Thread Jan Kiszka
Mathias Sundman wrote: ... No, I'm not used to OO languages, unfortunally. The reasons why I started to write this in C was: 1) I only know how to code in C, VisualBasic and Assembler. Assembler is out of the question, and I'm tired of VBs dependency for a bunch of DLLs. I like beeing able t

Re: Interface with GUI agent, was: Re: [Openvpn-devel] [Patch] revoke scripts were broken

2004-07-03 Thread Jan Kiszka
Denis Vlasenko wrote: On Saturday 03 July 2004 23:01, James Yonan wrote: management 127.0.0.1 20001 This will cause OpenVPN to listen on 127.0.0.1:20001 as its management interface port. It's important, of course, that the management port always be local, since we are using it to potentially

Re: Interface with GUI agent, was: Re: [Openvpn-devel] [Patch] revoke scripts were broken

2004-07-03 Thread Jan Kiszka
James Yonan wrote: ... Possible client -> server commands: (1) send auth credentials (2) get status (as in SIGUSR2) (3) send signal (SIGHUP, SIGUSR1, or SIGUSR2, SIGTERM) And server -> client commands: (1) need auth credentials -- GUI should query the user then return them to the daemon via

[Openvpn-devel] Re: Interface with GUI agent

2004-07-06 Thread Jan Kiszka
James Yonan wrote: ... If it's not a windows specific problem, then I suppost it's best to add the functionallity in the openvpn binary so we get the portability. I don't think the openvpn binary needs to know about this. But the service wrapper probably needs a second mode of operation, w

[Openvpn-devel] Re: Interface with GUI agent

2004-07-06 Thread Jan Kiszka
Mathias Sundman wrote: On Tue, 6 Jul 2004, Jan Kiszka wrote: James Yonan wrote: ... If it's not a windows specific problem, then I suppost it's best to add the functionallity in the openvpn binary so we get the portability. I don't think the openvpn binary needs to

Re: [Openvpn-devel] Re: Interface with GUI agent

2004-07-11 Thread Jan Kiszka
Mathias Sundman wrote: ... One more thing to consider... Should we consider a system running this service manager an open system where all locally logged on users is allowed to fully manage openvpn connections, which includes: * Start/Stop openvpn processes As a first step, I think we shoul

[Openvpn-devel] Re: Interface with GUI agent

2004-07-11 Thread Jan Kiszka
James Yonan wrote: I'm not sure that we really need a wrapper for unix, because most unix users will control OpenVPN by: (1) editing config files and starting from /etc/init.d, or (2) using some sort of GUI-based admin tool such as YaST and both of these methods are traditionally done as roo

Re: [Openvpn-devel] Re: Interface with GUI agent

2004-07-11 Thread Jan Kiszka
Denis Vlasenko wrote: 1. On Windows, if the the service wrapper has started some openvpn processes before our gui agent is started, how should find out about those processes? I can think of the following ways: 1a. Ask the service wrapper via the socket interface that I'm working on right now. T

[Openvpn-devel] incomplete system routing table

2004-09-12 Thread Jan Kiszka
Hi, on a Windows 2000 system, I'm facing troubles with setting the default gateway. The problem is that openvpn reports only two routing table entries in its log file: SYSTEM ROUTING TABLE 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=0 pr=2 a=0 h=0 m=1/1/1/1/1 127.0.0.1 255.255.255.255 127.0.0.1 p