Public bug reported:
>From the PR:
Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the root cause of
Public bug reported:
On Ubuntu 18.04 with the NVIDIA development repository PPA, installing
cuda-drivers I get the following error during the installation of
nvidia-390:
dpkg: error processing archive
/var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack):
trying to overwrite '
Since it requires control of the host, this cannot be done in Azure.
Control of the host is rather restricted there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1701222
T
We tested Xenial as well. Trusty is missing some other required
packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1643708
Title:
Add SPNEGO special case for NTLMSSP+Me
Bruce is saying that he tested Trusty as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1643708
Title:
Add SPNEGO special case for NTLMSSP+MechListMIC
Status in krb5 p
Filed https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1653278
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1643708
Title:
Add SPNEGO special case for NTLMSSP+MechListMI
This is needed for Ubuntu 14.04, 16.04, 16.10, and zesty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1653278
Title:
Update gss-ntlmssp to 0.7.0 to correct sequence number
Public bug reported:
gss-ntlmmssp sequence numbers are incorrect in 0.6.0. In 0.7.0 the
following patch (which is most of the difference between the two
versions) fixes sequence numbers. We discovered this testing OMI from
Linux to Windows, but don't have a simpler test case we can provide.
./ntl
This change in proposed corrects part of what is needed and makes the
Windows to Linux part of our scenario work. We will file a new bug to
pick up a change from gssntlmssp-0.6.0 to 0.7.0 to correct a sequence
numbering mismatch we've observed after applying this fix.
** Tags removed: verification
[Test Case]
create a file with some credentials:
$ echo F23:guest:guest > ~/ntlmcreds.txt
$ export NTLM_USER_FILE=~/ntlmcreds.txt
$ python
import gssapi
spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
tname = gssapi.raw.na
The test case in
https://github.com/krb5/krb5/pull/436#issuecomment-209017277 is the best
we can offer without going through the trouble of setting up OMI. We are
happy to test any preliminary builds, or -proposed, as necessary.
--
You received this bug notification because you are a member of Ub
Public bug reported:
MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
needs to implement specifically for the NTLMSSP mechanism. This is
required for compatibility with Windows services.
Upstream commit:
https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9
This is needed for Ubuntu 14.04, 16.04, and 16.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1643708
Title:
Add SPNEGO special case for NTLMSSP+MechListMIC
Status in kr
Public bug reported:
Customer using Lenovo P50 (Skylake) and Surface Book (Skylake) laptops
tried to start unity in a guest VM on Hyper-V. Kernel 4.4.0-31 started
as expected, Hyper-V drivers loaded as expected including the
framebuffer driver, plenty of memory and vCPUs allocated, but x.org
fails
Argh, this should be in linux-kernel, not systemd.
** Also affects: linux-kernel (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a mem
Public bug reported:
A sporadic hang with consequent crash is observed when booting Hyper-V
Gen1 guests...
Sauce request for upstream submission:
https://lkml.org/lkml/2015/10/15/673
>From Vitaly Kuznetsov <>
Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Date Thu,
16 matches
Mail list logo
