from:"Moritz Naumann"

[Touch-packages] [Bug 1704603] [NEW] Juniper/Pulse VPN (SSL VPN) not configurable

2017-07-15 Thread Moritz Naumann

Public bug reported:

While the OpenConnect CLI version available in Ubuntu 16.04.2 supports
connecting to (older but not current firmware versions of) Juniper/Pulse
VPN (SSL VPN) (using the --pulse option), the NM GUI does not allow for
configuring this type of VPN. You can choose to configure an OpenConnect
VPN, but it lacks the option to connect using the specific Juniper
Network Connect / Pulse Secure SSL VPN protocol.

Newer versions of network-manager-openconnect-gnome do, however, allow
for configuring this protocol and work with the openconnect '--protocol
pulse' option of the updated openconnect CLI.

Since Xenial is going to stay, and is the most likely target for
companies which make use of this VPN technology, please do consider to
support this protocol in Xenial by means of a SRU or backport.

The version of both openconnect and, moreover, the NM GUI, is most
likely not usable for any ompany running current VPN access servers
(with current software versions).

Thanks for your consideration.

** Affects: network-manager-openconnect (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: network-manager (Ubuntu) => network-manager-
openconnect (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1704603

Title:
  Juniper/Pulse VPN (SSL VPN) not configurable

Status in network-manager-openconnect package in Ubuntu:
  New

Bug description:
  While the OpenConnect CLI version available in Ubuntu 16.04.2 supports
  connecting to (older but not current firmware versions of)
  Juniper/Pulse VPN (SSL VPN) (using the --pulse option), the NM GUI
  does not allow for configuring this type of VPN. You can choose to
  configure an OpenConnect VPN, but it lacks the option to connect using
  the specific Juniper Network Connect / Pulse Secure SSL VPN protocol.

  Newer versions of network-manager-openconnect-gnome do, however, allow
  for configuring this protocol and work with the openconnect '--
  protocol pulse' option of the updated openconnect CLI.

  Since Xenial is going to stay, and is the most likely target for
  companies which make use of this VPN technology, please do consider to
  support this protocol in Xenial by means of a SRU or backport.

  The version of both openconnect and, moreover, the NM GUI, is most
  likely not usable for any ompany running current VPN access servers
  (with current software versions).

  Thanks for your consideration.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1481871] Re: apt-key del silenty fails to delete keys due to limited understanding of input formats

2016-01-03 Thread Moritz Naumann

This also affects Xenial (tested on yesterday's live installer).

** Summary changed:

- apt-key del doesn't understand fingerprint
+ apt-key del silenty fails to delete keys due to limited understanding of 
input formats

** Summary changed:

- apt-key del silenty fails to delete keys due to limited understanding of 
input formats
+ apt-key del silenty fails to delete keys due to limited understanding of GPG 
key ID formats

** Tags added: trusty xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1481871

Title:
  apt-key del silenty fails to delete keys due to limited understanding
  of GPG key ID formats

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  apt:
    Installed: 1.0.1ubuntu2.10

  apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
  7A82B743B9B8E46F12C733FA4759FA960E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here

  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still
  here

  # Works fine with IDs

  apt-key del  0E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported

  # Works fine with fingerprint on Precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1481871/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1481871] Re: apt-key del doesn't understand fingerprint

2016-01-02 Thread Moritz Naumann

I just ran into the same issue. What's not obvious from the original
post, though, is that apt-key reports back that it deleted the key "OK"
- but actually did not:


root@mybox:~# apt-key list | grep 79EAFD54
pub   1024D/79EAFD54 2009-01-22 [expired: 2013-06-28]

root@mybox:~# apt-key adv --keyid-format long --list-key 79EAFD54
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--homedir /tmp/tmp.0hGkImk1B8 --no-auto-check-trustdb --trust-model always 
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/xorg-edgers-ppa.gpg --keyid-format long --list-key 
79EAFD54
pub   1024D/BED1E87979EAFD54 2009-01-22 [expired: 2013-06-28]
uid  security OBS Project 

root@mybox:~# apt-key del BED1E87979EAFD54
OK

root@mybox:~# apt-key list | grep 79EAFD54
pub   1024D/79EAFD54 2009-01-22 [expired: 2013-06-28]


As such, if you supply a key ID as an argument to "apt-key del" in any GnuPG 
supported format other than the 'old' short key ID format without leading "0x" 
(so just the last 8 bytes of the key's fingerprint, ") the result is that your 
command is *silently ignored*.  (There seem to be some non-defined GPG formnats 
which will return an error message, such as when using the last 6 or 10 (but 
not 12) bytes of the fingerprint).

This can result in users and applications alike meaning to revoke trust
on an APT archive keyring, being told they succeeded in doing so, but
actually failing.

As such, from my perspective, this is a security bug.

This was Ubuntu 14.04.3 LTS x86_64 with the latest updates installed and
no held packages (but some third party PPAs).

I have not tried to reproduce this issue on any other Ubuntu releases. I
tried to reproduce this behaviour on Debian GNU/Linux 8.2 "Jessie" but
was unable to.

** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1481871

Title:
  apt-key del doesn't understand fingerprint

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  apt:
    Installed: 1.0.1ubuntu2.10

  apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
  7A82B743B9B8E46F12C733FA4759FA960E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here

  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still
  here

  # Works fine with IDs

  apt-key del  0E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported

  # Works fine with fingerprint on Precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1481871/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1039849] Re: Lightdm fails to start up after updates

2014-09-11 Thread Moritz Naumann

This is no longer an issue for me personally, since it's 2014 and I'm
running different software in different versions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1039849

Title:
  Lightdm fails to start up after updates

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  I've not been using this laptop for a while, but then I did, installed
  updates, rebooted, and ever since I'm running into failsafe X. I made
  some changes in between trying to see whether they would help it to
  load up (such as explicitly defining the driver in xorg.conf) but
  those didn't change the situation.

  I'm stuck now, not sure what to do, and would appreciate some hints. I
  asked for help in #ubuntu but since I don't know what exactly the
  problem is we didn't get anywhere really. If there's anything I can do
  to provide more information please let me know.

  This may be an issue related to gdm actually, since the only error
  message I can find now is in /var/log/gdm/:0.log:

  Fatal server error:
  Server is already active for display 0
  If this server is no longer running, remove /tmp/.X0-lock
  and start again.

  
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 

   ddxSigGiveUp: Closing log
  /var/log/gdm/:0.log (END)

  
  But maybe I missed something in the other relevant logs...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27
  Uname: Linux 3.2.0-30-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,mousepoll,snap,move,resize,wall,regex,vpswitch,imgpng,place,grid,session,unitymtgrabhandles,animation,expo,workarounds,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  Date: Wed Aug 22 04:37:18 2012
  DistUpgraded: 2012-04-27 20:57:28,759 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413.1)
  MachineType: ASUSTeK Computer Inc. UL30A
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-30-generic 
root=/dev/mapper/vg1-slash ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UdevDb: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  UpgradeStatus: Upgraded to precise on 2012-04-27 (116 days ago)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UL30A
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr211:bd10/20/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UL30A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1039849/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 719763] Re: Segfault in MixSomeSources at openal-soft-1.12.854/Alc/ALu.c:1033

2014-07-25 Thread Moritz Naumann

I'll respond in 3.5 years, please keep the bug open!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openal-soft in Ubuntu.
https://bugs.launchpad.net/bugs/719763

Title:
  Segfault in MixSomeSources at openal-soft-1.12.854/Alc/ALu.c:1033

Status in “openal-soft” package in Ubuntu:
  New

Bug description:
  While running a development revision of the MegaGlest game
  (http://megaglest.org), I have run into this segmentation fault:

  1033  /build/buildd/openal-soft-1.12.854/Alc/ALu.c: File or directory not 
found.
  Core was generated by `./glest.bin'.
  Program terminated with signal 8, Arithmetic exception.
  #0  MixSomeSources (ALContext=0x2bd41c0, DryBuffer=value optimised out, 
SamplesToDo=value optimised out) at 
/build/buildd/openal-soft-1.12.854/Alc/ALu.c:1033
in /build/buildd/openal-soft-1.12.854/Alc/ALu.c
  #0  MixSomeSources (ALContext=0x2bd41c0, DryBuffer=value optimised out, 
SamplesToDo=value optimised out) at 
/build/buildd/openal-soft-1.12.854/Alc/ALu.c:1033
  #1  0x7f9e0769b612 in aluMixData (device=0x7f9e091c8010, 
buffer=0x7f9df5536040, size=value optimised out) at 
/build/buildd/openal-soft-1.12.854/Alc/ALu.c:1373
  #2  0x7f9e076ac2b0 in stream_write_callback (stream=0x2bd2840, len=7104, 
pdata=value optimised out) at 
/build/buildd/openal-soft-1.12.854/Alc/pulseaudio.c:437
  #3  0x7f9e04683367 in pa_command_request (pd=value optimised out, 
command=value optimised out, tag=value optimised out, t=0x1d5a2460, 
userdata=0x2bcdc00) at pulse/stream.c:749
  #4  0x7f9e010196f6 in pa_pdispatch_run (pd=0x2bd0c60, packet=value 
optimised out, creds=value optimised out, userdata=0x2bcdc00) at 
pulsecore/pdispatch.c:331
  #5  0x7f9e0466aafd in pstream_packet_callback (p=value optimised out, 
packet=0x1fa23820, creds=0x2bd0f60, userdata=0x2bcdc00) at pulse/context.c:346
  #6  0x7f9e0101d564 in do_read (p=0x2bd0e10) at pulsecore/pstream.c:816
  #7  do_something (p=0x2bd0e10) at pulsecore/pstream.c:184
  #8  0x7f9e046783d3 in dispatch_pollfds (m=0x2b4d0b0) at 
pulse/mainloop.c:688
  #9  pa_mainloop_dispatch (m=0x2b4d0b0) at pulse/mainloop.c:933
  #10 0x7f9e04678808 in pa_mainloop_iterate (m=0x2b4d0b0, block=value 
optimised out, retval=0x0) at pulse/mainloop.c:964
  #11 0x7f9e046788b0 in pa_mainloop_run (m=0x2b4d0b0, retval=0x0) at 
pulse/mainloop.c:979
  #12 0x7f9e0468720b in thread (userdata=0x2b4aa30) at 
pulse/thread-mainloop.c:94
  #13 0x7f9e0102afb8 in internal_thread_func (userdata=0x2b4ab10) at 
pulsecore/thread-posix.c:83
  #14 0x7f9e08cf3971 in start_thread () from /lib/libpthread.so.0
  #15 0x7f9e04d8a92d in clone () from /lib/libc.so.6
  #16 0x in ?? ()

  I assume this is reproducible (I'm testing this now, takes a while).

  
  $ lsb_release -rd
  Description:  Ubuntu 10.10
  Release:  10.10

  $ LC_ALL=C apt-cache policy libopenal1
  libopenal1:
Installed: 1:1.12.854-2
Candidate: 1:1.12.854-2
Version table:
   *** 1:1.12.854-2 0
  500 http://de.archive.ubuntu.com/ubuntu/ maverick/universe amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/719763/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1704603] [NEW] Juniper/Pulse VPN (SSL VPN) not configurable

[Touch-packages] [Bug 1481871] Re: apt-key del silenty fails to delete keys due to limited understanding of input formats

[Touch-packages] [Bug 1481871] Re: apt-key del doesn't understand fingerprint

[Touch-packages] [Bug 1039849] Re: Lightdm fails to start up after updates

[Touch-packages] [Bug 719763] Re: Segfault in MixSomeSources at openal-soft-1.12.854/Alc/ALu.c:1033

5 matches

Site Navigation

Mail list logo

Footer information