[vpnc-devel] Status vpnc

[Joerg Mayer]

Hello,

after a way too long time of not merging patches and not even reading all
the mails on the list I've finally forced myself to change some sleeping
time into vpnc time. Things are more than back to full speed but that's
due to the backlog that has been collected.

I've looked into all the unread mails in my inbox although I have to properly
read two or three of them but then this should be the end of the backlog
as far as mails are concerned.

Plans:

I'll try to find and fix some bugs and then make a 0.5.2 release. I will
need help with most of these as I can't reproduce (most of) them. This
what's on my radar. In case you've reported a problem that's still present
in the svn trunk that isn't listed here, please tell us so.

- There are reports that pepole have to log in twice using xauth
  see https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/214399

  This bug is rather important as it hits kvpnc users quite badly.

  Unfortunately I can't reproduce it.

- Further research into the "packet too short" messages.
  see http://lists.unix-ag.uni-kl.de/pipermail/vpnc-devel/2005-February/000553.html
  for more information

  This might be fixed as a bug where keepalive messages were treated like
  normal messages war found and fixed.
  Unfortunately there has been one report already that it might not yet be
  fixed in all cases.

  Again, I don't see that problem so I need more info by people who are
  still affected.

- On Solaris (opensolaris) the route option needs another keyword when pointing
  to an interface. Fix this in a portable manner in vpnc-script.

- Make the mtu size patch to vpnc-script more portable (currently it's Linux
  only).

- There are at least two memory leaks remaining in the code. Fix them.

- Your bug might be here :-)

If you can help with any of these. Help could be by fixing them or providing a
good descripion on the circumstances of the bug or providing information how to
reproduce it or by testing the current svn trunk and letting us know that the
bug is still there (please provide the version info of vpnc and a uname -a of
the system).

This may take a few weeks, depending on the amount of time I and others
spend on the tasks above and on the usefulness of the problem reports.

With that out of the door, I'd like to merge the Nortel branch and the persist
stuff and make a 0.6.0 release. Especially the Nortel branch needs quite some
rework before merging (it's too invasive in my vew right now, but a more thorough
review might prove me wrong).

Stuff people have told me they are working on:

- (better) Netscreen support
- main mode support

This stuff will be merged when it exists and is ready for merging.

Ciao
   Joerg
-- 
Joerg Mayer                                           <jmayer at loplof.de>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.