On Thu, 07 Jun 2007 17:08:41 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:
>
> - "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
>> > Attaching a new version of my patch, this checks whether a private
>> key file is configured for the connection before attempting to read a
>> password from the key
- "Jon Nettleton" <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-06-07 at 12:08 -0400, Dan Williams wrote:
> > On Thu, 2007-06-07 at 16:42 +0100, Jon Escombe wrote:
> > > Any thoughts on applying the device-link-race patch to 0.6.x?
> >
> > Working on that now; I'd rather figure out why nm_device_
On Thu, 07 Jun 2007 17:08:41 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:
>
> - "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
>> > Attaching a new version of my patch, this checks whether a private
>> key file is configured for the connection before attempting to read a
>> password from the key
On Thu, 2007-06-07 at 12:37 -0400, Jon Nettleton wrote:
> On Thu, 2007-06-07 at 12:08 -0400, Dan Williams wrote:
> > On Thu, 2007-06-07 at 16:42 +0100, Jon Escombe wrote:
> > > - "Dan Williams" <[EMAIL PROTECTED]> wrote:
> > >
> > > > > I believe Tomas is using 6.4, which doesn't work (for him
On Thu, 2007-06-07 at 12:08 -0400, Dan Williams wrote:
> On Thu, 2007-06-07 at 16:42 +0100, Jon Escombe wrote:
> > - "Dan Williams" <[EMAIL PROTECTED]> wrote:
> >
> > > > I believe Tomas is using 6.4, which doesn't work (for him) because
> > > it always tries to get a password from the keyring
On Thu, 2007-06-07 at 16:42 +0100, Jon Escombe wrote:
> - "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
> > > I believe Tomas is using 6.4, which doesn't work (for him) because
> > it always tries to get a password from the keyring. 6.5 includes a
> > patch to never get a password from the keyri
- "Dan Williams" <[EMAIL PROTECTED]> wrote:
> > I believe Tomas is using 6.4, which doesn't work (for him) because
> it always tries to get a password from the keyring. 6.5 includes a
> patch to never get a password from the keyring (which I'm assuming
> would work for Tomas - but breaks the
On Thu, 2007-06-07 at 16:08 +0100, Jon Escombe wrote:
> - "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
> > > Attaching a new version of my patch, this checks whether a private
> > key file is configured for the connection before attempting to read a
> > password from the keyring. I believe this
- "Dan Williams" <[EMAIL PROTECTED]> wrote:
> > Attaching a new version of my patch, this checks whether a private
> key file is configured for the connection before attempting to read a
> password from the keyring. I believe this should suit both of the
> above 802.1X configuration types..
>
On Thu, 2007-06-07 at 12:42 +0100, Jon Escombe wrote:
> > Tomáš Hnyk wrote:
> >
> > >>
> > >> So out of interest, what fields do you use in the configuration
> > >> dialog? I am using "identity", "private key file," and "private key
> > >> password".
> > >>
> > >> Regards,
> > >> Jon.
> > >>
> > >
> Tomáš Hnyk wrote:
>
> >>
> >> So out of interest, what fields do you use in the configuration
> >> dialog? I am using "identity", "private key file," and "private key
> >> password".
> >>
> >> Regards,
> >> Jon.
> >>
> > The config windows should look like this:
> > http://eduroam.fjfi.cvut.cz/
Tomáš Hnyk wrote:
>>
>> So out of interest, what fields do you use in the configuration
>> dialog? I am using "identity", "private key file," and "private key
>> password".
>>
>> Regards,
>> Jon.
>>
> The config windows should look like this:
> http://eduroam.fjfi.cvut.cz/images/eduroam_linux2.p
On Thu, 07 Jun 2007 00:58:18 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:
> Tomáš Hnyk wrote:
>
>> Well, it is different from current developement version. But as stated
>> in the bug you have linked to, this should be much different in the
>> next version, so it does not matter anyway.
>> I
Tomáš Hnyk wrote:
> Well, it is different from current developement version. But as stated
> in the bug you have linked to, this should be much different in the next
> version, so it does not matter anyway.
> I actually found I am facing a completely opposite issue to yours: my
> password is no
Tomáš Hnyk wrote:
> Hi,
> I tried to apply your patch but it failed. After I investigated it a
> little, I found out you are probably using a distro-specific source.
> Could you please try this against the current svn? I am using Ubuntu
> with network manager 0.6.4 and there the patch fails as w
Hi,
I tried to apply your patch but it failed. After I investigated it a
little, I found out you are probably using a distro-specific source. Could
you please try this against the current svn? I am using Ubuntu with
network manager 0.6.4 and there the patch fails as well.
Tomas
On Wed, 06 Jun
I will try to test your patch, but, being the exam period now, I will not
get to school where I have similar issues untill next week, probably. Stay
tuned.
Tomas
On Wed, 06 Jun 2007 15:14:00 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:
>
> - "Jon Escombe" <[EMAIL PROTECTED]> wrote:
>>
>>
- "Jon Escombe" <[EMAIL PROTECTED]> wrote:
> - "Jon Escombe" <[EMAIL PROTECTED]> wrote:
> >
> > Symptom now is that on a first connection it works fine, dialog is
> > presented for the credentials and connects fine. However, once the
> > details for the network are in gconf, reconnecting
- "Jon Escombe" <[EMAIL PROTECTED]> wrote:
>
> Symptom now is that on a first connection it works fine, dialog is
> presented for the credentials and connects fine. However, once the
> details for the network are in gconf, reconnecting to that network
> just results in a endless loop of tryin
Hi, I think I am running into similar if nto the same issue:
http://mail.gnome.org/archives/networkmanager-list/2007-May/msg00192.html
Regards, Tomas Hnyk
On Tue, 05 Jun 2007 18:49:58 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:
> With the syslog buffer overflow fixed (thanks!), I've been able to
With the syslog buffer overflow fixed (thanks!), I've been able to test my WPA2
connection some more. Unfortunately it wasn't long before hitting another
problem.
Symptom now is that on a first connection it works fine, dialog is presented
for the credentials and connects fine. However, once t
21 matches
Mail list logo
