On Wed, 2005-12-07 at 02:47 +0100, Tim Niemueller wrote:
> I have just checked in NM-OpenVPN 0.3.1.
>
> I have applied Crispin's patch, also the login banner part. I will have
> a look at a nicer solution tommorrow.
I think I've taken care of this now, by setting last_attempt_success to
TRUE when
On Wed, 2005-12-07 at 01:46 +0100, Tim Niemueller wrote:
> > 2) Move higher-level key types to the applets, rather than keeping logic
> > for them in NetworkManager. Right now we have the constants for ASCII,
>
> Am I right if I say that we just define two interfaces, one which is
> nice for the
I have just checked in NM-OpenVPN 0.3.1.
I have applied Crispin's patch, also the login banner part. I will have
a look at a nicer solution tommorrow.
I have also added support for TCP connections. It is just another check
button in the optional information section. Does it still fit a 1024x768
sc
Dan Williams wrote:
> Hi,
Hi.
> 2) Move higher-level key types to the applets, rather than keeping logic
> for them in NetworkManager. Right now we have the constants for ASCII,
Am I right if I say that we just define two interfaces, one which is
nice for the machine which we will use for commu
Ryan Skadberg wrote:
> A quick request, can we add the ability to pick the protocol? Seems as
> if I use TCP and default is UDP and there is no option to pick TCP, so I
> can't seem to use this yet. I get a cannot connect to server error.
Yes, that's an easy one. I think for this I have to think
I really can't get used to the reply scheme...
Ryan Skadberg wrote:
> One more.
>
> I seem to have to enter a password to unlock my PEM. If I just do
Yes, if you have crypted your key this is true.
Code to deal with the management console is even in there already for
the password authenticatio
Trying once more.
Attached to this email is a patch adding NM support for Archlinux,
http://www.archlinux.org/ It should apply cleanly to the current cvs
version of NM.
Comments? Criticism? Thoughts?
Regards,
/Tor
nm-arch-20051206.patch.gz
Description: GNU Zip compressed data
On Sun, 2005-12-04 at 12:33 -0500, Paul Blazejowski wrote:
> Hello folks,
>
> Below is a cosmetic change to the way the rc script calls dbus. Patch is
> against CVS HEAD.
>
> Index: initscript/Slackware/rc.networkmanager
> ===
> RCS
On Tue, 2005-12-06 at 02:08 -0500, Paul Blazejowski wrote:
> By default dhcpcd is called (from /etc/rc.d/rc.inet1) to obtain an IP
> address, running NetworkManager will never get us an IP because dhclient
> is unable to bind to already taken interfce, so we kill any dhcpcd
> processes in order to
On Mon, 2005-12-05 at 13:33 -0500, Dan Williams wrote:
> On Sun, 2005-12-04 at 22:24 +0100, Tor Krill wrote:
> > Sorry, i completely missed the changelog in the openvpn directory :-(
> >
> > Is there an easy way to disable build of openvpn?
>
> AFAIK, they actually don't get built by default. I
On Tue, 2005-12-06 at 19:57 +, Crispin Flowerday wrote:
> 2) The gconf 'last_attempt_success' flag is never set to true. This is
> due to the fact that it is only set via the login_banner dbus message,
> however openvpn doesn't pass a login_banner in the IP4_CONFIG message. I
> can't see an eas
Hi,
So in the search for WPA (I know it's here somewhere...), there need to
be some API changes for NetworkManager. These are related to key types
and auth algorithms, and shouldn't impact core functionality much for
apps the depend on NM.
However, I've taken this as an opportunity to look close
Tim,
NM-OpenVPN 0.3 is working wonderfully, except for one slight issue - it
fails to remember the password, I have tracked this down to 2 issues:
1) The auth dialog is expecting 2 passwords in the keyring manager,
however only one is stored in the openvpn implementation
2) The gconf 'last_attem
13 matches
Mail list logo
