wireless lan encryption key

[fire-fly]

Hi
anybody know well the wireless lan encryption key kept ? I need to know. Thanks !
Cheers
Fire-fly

[Quella]

Are you asking where it is stored on your Access Point or on the Fedora Box?

Quella

[brunson]

On the fedora box it's either kept in clear text in a root read-only file if you configure it using system-config-network. If you use NetworkManager it's stored in your encrypted keyring.

[fire-fly]

Are you asking where it is stored on your Access Point or on the Fedora Box?

Quella
on the Fedora Box

[tox_yray]

See brunson's post. To have access to you keyring, you gotta have the keyring manager.

It's either in Applications -> System Tools OR installable by yum.

[fire-fly]

See brunson's post. To have access to you keyring, you gotta have the keyring manager.

It's either in Applications -> System Tools OR installable by yum.
I need that, but after the inital confuration, the next time systm-config-network needs to retrive it from some location. But from where ? :D

[tox_yray]

You can see the key in the keyring... I don't know if you need to retreive it for a program or whatever but if it is just to see it, you just need to get in the kyring manager.

[fire-fly]

You can see the key in the keyring... I don't know if you need to retreive it for a program or whatever but if it is just to see it, you just need to get in the kyring manager.

Hi
Thanks for the help.

Let me explain why i need to know the key's location, may be you or anybody can shared a better solution. I move around alot. However, every wireless base station, has either different key asigned to me or no key used but my mac address is in their base station. Differen ESSID etc.

Now. I wanted to execute a script to configure it, and connect ot the base station. Instead of using system-config-network gui. Is too trouble some.

Any suggestion, thanks
? :D

[tox_yray]

Oh, well... If it is to configure a script to connect to the base station, I suggest either two things:

1) Use NetworkManager (not system-config-network, NetworkManager). It works fine here to switch between many networks (including a network that filter MAC adresses, so that'll work too). NetworkManager stores its keys in the keyring and does the key managing for you. Way easier than scripting your own stuff...

2) If you don't want to use the NetworkManager, I guess you will have to find a way to either access the keyring via scripting OR hardcoding your keys in the scripts (which is NOT a secure way to do it, but if you aren't preoccupied by security you could use it as a viable solution)

Hope this helps :)

[Brian1]

Ok the files you need to modify are /etc/sysconfig/networking-scripts/ifcfg-eth* and /etc/sysconfig/netorking-scripts/keys-eth*

The way I would do it if modifying the the files with an editor seems difficult then I would create your normally most used setup. Once setup and working fine then make copies of the two files so you can use them in a script. Rename them to something that makes sense like ifcfg-eth1 to ifcfg-eth1-name_of_site. Now in a script you just need to bring down the interface with the command ifdown eth* and replace the files and bring up the interface with ifup command. Example of flowchart for script.

ifdown eth1
cp /etc/sysconfig/networking-scripts/ifcfg-eth1-work_site_1 /etc/sysconfig/networking-scripts/ifcfg-eth1
cp /etc/sysconfig/networking-scripts/keys-eth1-work_site_1 /etc/sysconfig/networking-scripts/keys-eth1
ifup eth1

If no keys are needed then do something like ' rm cp /etc/sysconfig/networking-scripts/keys-eth1

Do the same for all connections. With the simpliest of these scripts it needs to run as root.

Brian1

[fire-fly]

Ok the files you need to modify are /etc/sysconfig/networking-scripts/ifcfg-eth* and /etc/sysconfig/netorking-scripts/keys-eth*

The way I would do it if modifying the the files with an editor seems difficult then I would create your normally most used setup. Once setup and working fine then make copies of the two files so you can use them in a script. Rename them to something that makes sense like ifcfg-eth1 to ifcfg-eth1-name_of_site. Now in a script you just need to bring down the interface with the command ifdown eth* and replace the files and bring up the interface with ifup command. Example of flowchart for script.

ifdown eth1
cp /etc/sysconfig/networking-scripts/ifcfg-eth1-work_site_1 /etc/sysconfig/networking-scripts/ifcfg-eth1
cp /etc/sysconfig/networking-scripts/keys-eth1-work_site_1 /etc/sysconfig/networking-scripts/keys-eth1
ifup eth1

If no keys are needed then do something like ' rm cp /etc/sysconfig/networking-scripts/keys-eth1

Do the same for all connections. With the simpliest of these scripts it needs to run as root.

Brian1
Hi Brian1
Thanks! I should have checkd more carefully /etc/sysconfig/networking-scripts missing the file call key-eth1.
I am using the technique you suggest except I use symbolic link instead of copy.
Thanks
fire-fley