By storing passphrases and secrets in the "default" keyring,
networkmanager makes it harder to separate keyrings by functionality:
GPG,SSH,NM...
For example, I consider network passphrases trivial enough to be
unlocked on startup by the master gnome-keyring password, but not GPG
or SSH keys.
So my
Obviously, I hadn't finished:
> VPN connections
> . I have yet to create VPNs through network manager, but once
> created I assume they would be given a
a title-area on the same logical level as the "Wired" and "Wireless"
network areas. This is why I recommend the full horizontal rule be
saved un
>> But most of them do have a more or less technical background. The users I am
>> thinking about are really native end users.
Ubuntu has very many users and it's polished easy-to-use interface
does not target technical proficiency. The problem is contacting the
users - perhaps a survey concerning
Resending this message, forgot to cc the networkmanager mailing-list.
Stupid gmail (or me). In any case, is this thread worth filing an RFE
on bugzilla ?
On Tue, Mar 2, 2010 at 2:25 AM, Dan Williams wrote:
> On Sun, 2010-02-28 at 16:45 -0500, Yclept Nemo wrote:
>> Quick question
Quick question, can the dispatcher scripts in
"/etc/NetworkManager/dispatcher.d/*" be run when:
down) only when no more public interfaces remain
up) only when the first public interface is brought up
I say "public" because iirc via consolekit some network connections
can be exclusive to starting
The tap0 device is created by openvpn but not pushed any network details -
openvpn expects a dhcp client to lease an IP.
When NetworkManager sees the device:
Sep 9 11:41:09 cinnabar nm-system-settings: Added default wired connection
'Auto tap0' for /org/freedesktop/Hal/devices/net_de_c1_d5_98_e6_
