Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #167855 > unrolled thread

Network manager (again)

Back to article view | Back to linux.debian.user

Contents

  Network manager (again) Bhasker C V <bhasker@unixindia.com> - 2016-05-14 05:30 +0200
    Re: Network manager (again) Hans <hans.ullrich@loop.de> - 2016-05-14 06:50 +0200
      Re: Network manager (again) Re: Rodary Jacques <rodaryj@free.fr> - 2016-05-17 03:30 +0200
        Re: Network manager (again) Re: David Wright <deblis@lionunicorn.co.uk> - 2016-05-17 16:10 +0200
    Re: Network manager (again) Michael Biebl <biebl@debian.org> - 2016-05-16 04:40 +0200
    Re: Network manager (again) David Wright <deblis@lionunicorn.co.uk> - 2016-05-16 05:00 +0200

#167855 — Network manager (again)

Hi

  I am finding it difficult to settle on a good network manager which
can work for my case

1. My home dir is luks/ext4 and mounted manually after logging in for
the first time
2. My GUI is started after mounting my home dir and by manual startx only

I could never get my network manager to store passwords in the user dir.
I do not like the passwords stored in
/etc/NeworkManager/sytem-connections with plain passwords visible so
anybody can open them if they have physical access to the machine/disk
(usb live stick etc., )

If I pull up the properties of nm-applet and change the option to 
"Store password only for this user", nm-applet does not connect since
the keyring is no automatically unlocked due to startx

Can anyone help me with fixing this network-manager so the passwords are
stored per-user in my luks home rather than /etc/...  OR tell me how to
enable nm-applet to automatically trigger opening gnome-keyring ?

-- 
Bhasker C V
Secure Mails: 
http://pgp.mit.edu/pks/lookup?op=get&search=0x4D05FEEC54E47413
Registered Linux User: #306349 

[toc] | [next] | [standalone]

#167857

Am Samstag, 14. Mai 2016, 05:27:06 schrieb Bhasker C V:

Hi,
try wicd (vicd-ncurses, wicd-gtk, wicd-cli). It may fit your needs. And you can 
have entries in /etc/network/interfaces, so you can be already connected 
without any window-manager.

Good luck!

Hans
> Hi
> 
>   I am finding it difficult to settle on a good network manager which
> can work for my case
> 
> 1. My home dir is luks/ext4 and mounted manually after logging in for
> the first time
> 2. My GUI is started after mounting my home dir and by manual startx only
> 
> I could never get my network manager to store passwords in the user dir.
> I do not like the passwords stored in
> /etc/NeworkManager/sytem-connections with plain passwords visible so
> anybody can open them if they have physical access to the machine/disk
> (usb live stick etc., )
> 
> If I pull up the properties of nm-applet and change the option to
> "Store password only for this user", nm-applet does not connect since
> the keyring is no automatically unlocked due to startx
> 
> Can anyone help me with fixing this network-manager so the passwords are
> stored per-user in my luks home rather than /etc/...  OR tell me how to
> enable nm-applet to automatically trigger opening gnome-keyring ?

[toc] | [prev] | [next] | [standalone]

#167933 — Re: Network manager (again) Re:

[Multipart message — attachments visible in raw view] — view raw

Le samedi 14 mai 2016, 06:47:11 Hans a écrit :
> Am Samstag, 14. Mai 2016, 05:27:06 schrieb Bhasker C V:
> 
> Hi,
> try wicd (vicd-ncurses, wicd-gtk, wicd-cli). It may fit your needs. And you
> can have entries in /etc/network/interfaces, so you can be already
> connected without any window-manager.
> 
> Good luck!
> 
> Hanspoint d'accès wifi
> 
> > Hi
> > 
> >   I am finding it difficult to settle on a good network manager which
> > 
> > can work for my case
> > 
> > 1. My home dir is luks/ext4 and mounted manually after logging in for
> > the first time
> > 2. My GUI is started after mounting my home dir and by manual startx only
> > 
> > I could never get my network manager to store passwords in the user dir.
> > I do not like the passwords stored in
> > /etc/NeworkManager/sytem-connections with plain passwords visible so
> > anybody can open them if they have physical access to the machine/disk
> > (usb live stick etc., )
> > 
> > If I pull up the properties of nm-applet and change the option to
> > "Store password only for this user", nm-applet does not connect since
> > the keyring is no automatically unlocked due to startx
> > 
> > Can anyone help me with fixing this network-manager so the passwords are
> > stored per-user in my luks home rather than /etc/...  OR tell me how to
> > enable nm-applet to automatically trigger opening gnome-keyring ?
I don't understand why you suggest using packages said unstable by debian's package installer? I 
had also such advice for my "point d'accès wifi" question.

[toc] | [prev] | [next] | [standalone]

#167952 — Re: Network manager (again) Re:

On Tue 17 May 2016 at 03:07:48 (+0200), Rodary Jacques wrote:
> Le samedi 14 mai 2016, 06:47:11 Hans a écrit :

> > Am Samstag, 14. Mai 2016, 05:27:06 schrieb Bhasker C V:
> > try wicd (vicd-ncurses, wicd-gtk, wicd-cli). It may fit your needs. And you
            w ^
> > can have entries in /etc/network/interfaces, so you can be already
> > connected without any window-manager.

> > >   I am finding it difficult to settle on a good network manager which
> > > can work for my case

> I don't understand why you suggest using packages said unstable by debian's package installer? I 
> had also such advice for my "point d'accès wifi" question.

Could we have a reference please for "said unstable by debian's package installer"?
(I assume you're talking about the wicd packages, because someone wrote
"Please note, an entry does not work with network-manager. Use wicd instead"
in the thread called "WiFi Access Point".)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#167886

[Multipart message — attachments visible in raw view] — view raw

Am 14.05.2016 um 05:27 schrieb Bhasker C V:
> Hi
> 
>   I am finding it difficult to settle on a good network manager which
> can work for my case
> 
> 1. My home dir is luks/ext4 and mounted manually after logging in for
> the first time
> 2. My GUI is started after mounting my home dir and by manual startx only
> 
> I could never get my network manager to store passwords in the user dir.

This works just fine here, out-of-the-box using GNOME3.

passwords can be system-owned (stored in
/etc/NetworkManager/system-connections) which have the benefit of being
available during early boot or agent/user-owend, i.e. they are stored in
the users keyring.
For that the user needs to be logged into the desktop environment.
You can configure this easily via nm-connection-editor on a
per-connection basis.

GNOME3 uses gnome-keyring which is started automatically and unlocked if
you have libpam-gnome-keyring installed (assuming the login password and
keyring password are the same). libpam-gnome-keyring will most likely
not work if you use startx. Fwiw, I strongly recommend to use a display
manager.

If you use a different desktop environment, you might have to start
gnome-keyring manually and unlock the keyring on your own, or don't use
a passphrase for your gnome keyring, which should be okayish, since you
luks encrypt your home.
You can change the password for your gnome keyring using the seahorse tool.
The start of gnome-keyring is handled via
/etc/xdg/autostart/gnome-keyring-*.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [next] | [standalone]

#167896

On Sat 14 May 2016 at 05:27:06 (+0200), Bhasker C V wrote:
>   I am finding it difficult to settle on a good network manager which
> can work for my case
> 
> 1. My home dir is luks/ext4 and mounted manually after logging in for
> the first time
> 2. My GUI is started after mounting my home dir and by manual startx only
> 
> I could never get my network manager to store passwords in the user dir.
> I do not like the passwords stored in
> /etc/NeworkManager/sytem-connections with plain passwords visible so
> anybody can open them if they have physical access to the machine/disk
> (usb live stick etc., )
> 
> If I pull up the properties of nm-applet and change the option to 
> "Store password only for this user", nm-applet does not connect since
> the keyring is no automatically unlocked due to startx
> 
> Can anyone help me with fixing this network-manager so the passwords are
> stored per-user in my luks home rather than /etc/...  OR tell me how to
> enable nm-applet to automatically trigger opening gnome-keyring ?

Like Hans, I use wicd (wicd-curses) because I only run a window manager.
These suggestions are completely untested but might be worth a shot.
You could create /home/wicd/ and copy /etc/wicd/* into it, then move
/etc/wicd to /etc/wicd-preserve and create a symlink /etc/wicd -> /home/wicd
If it all still works like that, shred and remove /etc/wicd-preserve.

The main issue AFAICT is making the wicd-daemon start only after /home
is mounted (and stop appropriately if you want to unmount it again).
I don't know systemd well enough to know if that's trivial or hard.
But the main thing is that it puts wicd/*.conf safely onto your
encrypted /home.

You might be able to coerce NM in the same way; I have no idea.

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web