[Vpn-help] Some suggestion for 2.x

[Matthew Grooms]

Massimo Uliana wrote:
> Hi,
>    this week I tested a lot the with the 1.1 RC 4 version. My
> impression is that this version is stable and I don't have bug to
> report.
> However, while I was using the Shrew VPN client 1.1, I notice that
> same little GUI features was missing. I'm not a developer but, as a
> user, I think same refinements in the GUI could lead to a better user
> experience.
> So here my suggestions for the 2.x release(or my wish list).
> 
> - Have the ability(may be in a preference menu) to automatically start
> the try icon at user loging.
> 
> - When rigth-clicking on the icon could appear something like this:
> 
> Connect to -> | Site 1...
> Preference     | Site 2...
> About
> ---------------
> Exit
> 
> Where Site 1, Site 2 are pre-configured sites with "VPN Manager"
> application. When you select a site the  "VPN connect" application
> appear.
> 
> - When the the "VPN connect" application is "connected" to a site have
> the ability to put it in background(eg . simply by pressing a "ok"
> button) and resume it with the try icon or with "VPN Manager"
> application.
> 
> Ok, I stop here. I hope I don't annoy you.
> Bye

Massimo,

	Not at all. Good suggestions like these will certainly find their way 
into the product faster than you may think. Please keep them coming. I 
want the software to be as feature complete as possible. As a solo 
developer, I certainly can't think of everything that a potential user 
would find useful. Some interface changes will unfortunately need to 
take a back seat to other things. Its not that they are aren't 
important, but my priorities need to be maintained for the moment.

	The 2.x code base has already seen some massive changes and I will 
update the road map after the 1.1 release to let people know where I'm 
at. There are two major goals for this series. The first is to finalize 
the kernel driver feature set so they can be stabilized and certified by 
microsoft. The second is finish un-bundling the internal ike and ipsec 
implementations. This allows the security processing to be moved into 
the kernel and for the service to operate as a stand-alone ike daemon. 
The latter will be open sourced and ported to *nix as an alternative to 
racoon.

Thanks,

-Matthew