[Bug 1283663] Re: when using openvpn the vpn's dns is never used (DNSLEAK)

2015-03-18 Thread bitinerant
@mubtcez:  to use the OpenVPN server's pushed DNS servers, add this to
your .conf file:

script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf

If you want to use your own DNS servers, add the above plus a line for
each DNS server:

dhcp-option DNS 8.8.8.8

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1283663

Title:
  when using openvpn the vpn's dns is never used (DNSLEAK)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openvpn/+bug/1283663/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2015-03-17 Thread bitinerant
Actually, I'd like to retract part of what I said above.  Via tcpdump, I
was able to confirm that --push on the server for "dhcp-option DNS ..."
and "redirect-gateway" ARE ACTUALLY WORKING, though the changes are not
visible in /etc/resolv.conf. Rather, they are updated in dnsmasq and
resolv.conf points to dnsmasq.  (I don't think the "def1" flag for
"redirect-gateway" works.)

In my view, two things are needed:  (1) a documented way to view the
list of DNS servers within Network Manager's dnsmasq so folks here can
watch what is happening without tcpdump, and (2) support for "dhcp-
option DNS ..." and "redirect-gateway" on the client (not just options
pushed from the server).  The first item seems more important and should
be much easier.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2015-03-13 Thread bitinerant
Whether this is a bug or feature request, I don't know, but to be sure,
it is possible to do this with a .conf file and "sudo service openvpn
start" and not possible to do it via network-manager-openvpn (unless you
count disabling dnsmasq--I'm curious what side effects this has).  As
described in the original report, I have verified that these lines in a
.conf file allow the server to configure DNS (as long as the server
pushes 3 or more DNS servers):

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

but network-manager-openvpn does not support the 'up' and 'down'.

This same issue was addressed here:

  http://askubuntu.com/questions/519920/how-to-run-an-up-script-using-
network-manager-openvpn

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 771264] [NEW] error creating certificate which expires after 2038

2011-04-26 Thread bitinerant
Public bug reported:

Binary package hint: openvpn

When generating a new certificate, if the variables CA_EXPIRE or
KEY_EXPIRE put the expiration date after 19-Jan-2038, then pkitool will
create a certificate which expires around 1902 and also corrupt
keys/index.txt so that the next certificate to be generated will receive
the error "entry nn: invalid expiry date" and fail.

** Affects: openvpn (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/771264

Title:
  error creating certificate which expires after 2038

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

2010-02-05 Thread bitinerant
This one bit me when I deleted my old ssh keys and generated new ones on
Karmic.  Both work-arounds worked for me (I tried them
individually)--adding the line "export SSH_AUTH_SOCK=0" to ~/.bashrc OR
running "ssh-add ~/.ssh/id_rsa".  I like the latter better because it
doesn't require extra work to distribute to the systems I use.

-- 
ssh Agent admitted failure to sign using the key on big endian machines
https://bugs.launchpad.net/bugs/201786
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs