RE: Secrets D-Bus Interface

["Philip A. Culver" <pculver bostonatlantic net>]

I can do the same on my desktop.  The target system has a custom UI and no
connection editor other then the one coded into our product UI.  It is very
bizarre for me.  All other fields get saved.  I set wep-key2 to the key and
set the wep-tx-keyidx to 2 as well and only the wep-key2 gets saved in the
file.  

Does the nm-system-settings daemon have a debug mode that will log more
messages? 

Phil

-----Original Message-----
From: Dan Williams [mailto:dcbw redhat com] 
Sent: Tuesday, March 03, 2009 4:11 PM
To: Philip A. Culver
Cc: networkmanager-list gnome org
Subject: RE: Secrets D-Bus Interface

On Tue, 2009-03-03 at 14:51 -0500, Philip A. Culver wrote:
> Hi,
> 
> I have tracked my issue down a little further.  It seems my problem is
more
> on the Update side then retrieval.  I pass down a settings block and
> everything except wep-tx-keyidx is saved to the file in system-settings.
> wep-tx-keyidx is still 0 in the file.  Could you point me where in the
code
> this is handled so I can verify I am passing everything correctly.  No
> errors are thrown the value just isn't committed.  At this point I am
> assuming I am missing some subtlety in the DBus API.

Hmm, I just used the connection editor to save a system connection with
WEP index 3 and did get the expected wep-tx-keyidx=2 in my keyfile
connection.  Just to try to narrow down the issue, could you try to
create a system connection using the connection editor and set the wep
index to something other than the default, save the keyfile, and see
what you get?

Dan

> Thanks,
> Phil
> 
> -----Original Message-----
> From: Dan Williams [mailto:dcbw redhat com] 
> Sent: Thursday, February 26, 2009 7:06 PM
> To: Philip A. Culver
> Cc: networkmanager-list gnome org
> Subject: RE: Secrets D-Bus Interface
> 
> On Thu, 2009-02-26 at 18:51 -0500, Philip A. Culver wrote:
> > Hi Dan,
> > 
> > I call Connection.GetSettings to get the map of settings.  The
> > "wep-tx-keyidx" value is not in the 802-11-wireless-security submap.
This
> > is being called from a process running as root.
> 
> Is the key index is the 'default' value (ie, 0) it won't necessarily
> show up in the dict because default values don't.  If the key index in
> the keyfile is either 1, 2, or 3, then I'd expect it to show up, and not
> showing up in the GetSettings response would be a bug.
> 
> Dan
> 
> > I will double check in the morning that I am setting the value properly
> when
> > creating the connection.  I do see the entry in the file created by the
> > keyfile plugin in the system-settings directory.
> > 
> > Thanks,
> > Phil 
> > 
> > 
> > -----Original Message-----
> > From: Dan Williams [mailto:dcbw redhat com] 
> > Sent: Thursday, February 26, 2009 11:14 AM
> > To: Philip Culver
> > Cc: networkmanager-list gnome org
> > Subject: Re: Secrets D-Bus Interface
> > 
> > On Wed, 2009-02-25 at 16:42 -0500, Philip Culver wrote:
> > > Hi,
> > > 
> > > I was hoping someone here could help me out.  I need to obtain the
> > > currently configured WEP Key Index for a system connection stored via
> > > the keyfile plugin.   This setting doesn't come with the normal
> > > Connection properties so I assume I need to query the Secrets
interface
> > > to do so.   I am not sure what values I need to pass for the
> > > setting_name and hints parameters to retrieve this value.  I have
tried
> > > a few different combinations without success.
> > 
> > The WEP key index ("wep-tx-keyidx") should come through with the rest of
> > the connection settings, as long as it's set in the connection.  Is that
> > not what you're seeing?
> > 
> > Dan
> > 
> > 
>