** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2031942
Title:
AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
Status
** Description changed:
[Impact]
* User of openssh reported an issue that affects Lunar and Jammy.
* This crash is caused by the wrong pointer manipulation in the if
statement. The fix is to change the code to check if the value pointed
to by the pointer 'charptr' is NULL.
** Description changed:
[Impact]
* User of openssh reported an issue that affects Lunar and Jammy.
* This crash is caused by the wrong pointer manipulation in the if
statement. The fix is to change the code to check if the value pointed
to by the pointer 'charptr' is NULL.
** Description changed:
[Impact]
* User of openssh reported an issue that affects Lunar and Jammy.
* This crash is caused by the wrong pointer manipulation in the if
statement. The fix is to change the code to check if the value pointed
to by the pointer 'charptr' is NULL.
** Description changed:
[Impact]
* User of openssh reported an issue that affects Lunar and Jammy.
* This crash is caused by the wrong pointer manipulation in the if
statement. The fix is to change the code to check if the value pointed
to by the pointer 'charptr' is NULL.
** Description changed:
[Impact]
* User of openssh reported an issue that affects Lunar and Jammy.
* This crash is caused by the wrong pointer manipulation in the if
statement. The fix is to change the code to check if the value pointed
to by the pointer 'charptr' is NULL.
** Description changed:
+ [Impact]
+
+ * User of openssh reported an issue that affects Lunar and Jammy.
+
+ * This crash is caused by the wrong pointer manipulation in the if
+ statement. The fix is to change the code to check if the value pointed
+ to by the pointer 'charptr' is NULL.
+
+
I wanted to make sure again if my reasoning was correct (I guess it was), so I
did rebuild in 2 PPAs.
The ppc64el build failed, I did re-run the build and it failed again, so it is
reproducible.
Due to FTBFS we need to keep disabling LTO.
New PPAs (named more explicitly, so now there is no
Hi @Steve/@Vorlon
Could you help me identify where I might make a mistake in my
investigation in Heimdal? I am writing that comment after a month again,
because I would love to gain more knowledge and know where I was wrong.
Thank you in advance
--
You received this bug notification because
Moreover here are my 2 PPAs that has been compared:
https://launchpad.net/~michal-maloszewski99/+archive/ubuntu/heimdal-test-ppa2-michal
https://launchpad.net/~michal-maloszewski99/+archive/ubuntu/test-heimdal-lto-michal-ppa1
--
You received this bug notification because you are a member of
Checked the builds that seem to show they are good without delta vs the
originally reported bug
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936
Checking the non-lto PPA the two changelogs are now matching:
$ dpkg -x
Public bug reported:
After heimdal merge process, I was trying to figure out if the delta that is
still not dropped is required or not.
So, to test it, I have created 2 PPAs, one in which lto is disabled, and the
second one, where the lto is enabled. I have built them and downloaded the debs
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1912256
Title:
Missing channel binding prevents authentication to ActiveDirectory
Status
First of all, I have changed the SRU description in 'Test Plan' section a bit,
to be more precisely. We could assume the fix didn't work if I would leave it
as it did before.
I've added information that we should look for the changes within the specific
area in the manpage, so the steps are
** Description changed:
[Impact]
The problem here is straightforward.
The case is to fix manpages. They need to reflect a change done to the code
some time ago. That problem might be annoying for users before being fixed.
Backport upstream fix to Focal
Origin:
** Description changed:
[Impact]
The problem here is straightforward.
The case is to fix manpages. They need to reflect a change done to the code
some time ago. That problem might be annoying for users before being fixed.
Backport upstream fix to Focal
Origin:
** Description changed:
[Impact]
- The problem here is straightforward.
- The case is to fix manpages. They need to reflect a change done to the code
some time ago. That problem might be annoying for users before being fixed.
+ The problem here is straightforward.
+ The case is to fix
Retrigerred tests and no regressions now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465
Title:
ssh_config(5) contains outdated information
Status in openssh
** Description changed:
+ [Impact]
+
+ Path to samba-bgqd is wrong on 22.04.
+ Changing from /usr/lib*/samba/samba-bgqd into
/usr/lib/@{multiarch}/samba/samba-bgqd to align different architectures.
+ The @{multiarch} was initialized at the code before.
+ Before fixing it might confuse users
Updated bug description with:
Moreover, the dmesg output failed and it has showed that the 'k' flag is
required for the *.tdb files within /etc/apparmor.d/abstractions/samba.
It is required to close that bug in professional way, because the flag
is also affected by samba-bgqd.
** Description
** Description changed:
See bug here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1191532
Fix was backported, but the path to samba-bgqd is wrong on 22.04.
Currently apparmor profile has it like this:
/usr/lib*/samba/samba-bgqd
When in fact 22.04 has it on
Waiting for a review of MP
** Changed in: apparmor (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
Title:
** Changed in: libmnl (Ubuntu Jammy)
Assignee: Michał Małoszewski (michal-maloszewski99) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Ti
Set is as a 'Won't Fix'.
Assigning the Jammy part of the bug to Nobody.
I think there is no urgent case to take care of it now, if there exists a real
workaround.
In any trouble and in case of problem which will be still felt, please reach
out to me
and I will continue with the SRU.
--
You
** Changed in: libmnl (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for
Hi Lars,
As you probably know, that bug has been fixed in kinetic. Therefore, I might
prepare backporting and upload changes into Jammy.
The bug heat measure is low and I need additional data whether there are others
affected by that bug. The process of backporting (SRU) bears the risk so
** Description changed:
+ [Impact]
+
+ The problem here is straightforward.
+ The case is to fix manpages. They need to reflect a change done to the code
some time ago. That problem might be annoying for users before being fixed.
+
+ Backport upstream fix to Focal
+ Origin:
+
MP in inner review for some days
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465
Title:
ssh_config(5) contains outdated information
Status in openssh package in
Sure. I am ready to deeply investigate it to make a proper decision.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl
Work in progress on MP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
I am about to create a branch of it and send the MP.
I have simply used grep to check where /usr/lib*/samba/samba-bgqd occurs when I
did checkout to the ubuntu/jammy and I've seen that these files where it occurs
are in apparmor profile. I have changed apparmor profile to adapt it to the
actual
Both Hirsute and Impish are End of Life.
So there is no possibility to fix these ones.
Change will be SRUd to Focal for sure.
** Changed in: openssh (Ubuntu Hirsute)
Status: Triaged => Won't Fix
** Changed in: openssh (Ubuntu Impish)
Status: Triaged => Won't Fix
--
You
** Changed in: openssh (Ubuntu Focal)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
** Changed in: openssh (Ubuntu Hirsute)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
** Changed in: openssh (Ubuntu Impish)
Assignee: (unas
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
** Changed in: apparmor (Ubuntu Jammy)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
--
You received this bug notification because you are a member of
** Changed in: libmnl (Ubuntu Jammy)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Ti
36 matches
Mail list logo
