Hi!
On Mon, 2025-01-20 at 13:21:32 -0700, Sam Hartman wrote:
> TL;DR: Is it time for the rest of Debian to stop conforming to HURD's
> lack of maximums for path and hostname? By thispoint I think we
> recognize those lack of maximums as an anti-pattern for DOS prevention
> and other security reaso
Sam Hartman, le lun. 20 janv. 2025 17:12:05 -0700, a ecrit:
> The pam 1.5.3 hurd compatibility patch simply defines PATH_MAX to 4096.
> I believe that previous krb5 patches have done something similar.
> I think this approach is quite common to how people approach HURD
> compatibility.
Yes, and t
> "Samuel" == Samuel Thibault writes:
Samuel> And unfortunately, code that just uses PATH_MAX as
Samuel> allocation size most often do not really take care about
Samuel> this case, and then get possibly vulnerable.
Right, I'm just not sure the HURD approach is better.
The pam 1.
Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-markup
Version : 1.0.3
Upstream Contact: Anton Bachin
* URL : https://github.com/aantron/markup.ml
* License
Sam Hartman, le lun. 20 janv. 2025 15:48:00 -0700, a ecrit:
> My restatement is that it's possible to create paths where the full path
> name is longer than PATH_MAX.
>
> I guess a better way to look at this would be that paths beyond PATH_MAX
> may break.
And unfortunately, code that just uses P
> "Samuel" == Samuel Thibault writes:
Samuel> Hello, Sam Hartman, le lun. 20 janv. 2025 13:21:32 -0700, a
Samuel> ecrit:
>> I will admit I was kind of disappointed that rather than working
>> to make my package handle arbitrary hostnames, the patch simply
>> introduced an
Please test pam from experimental.
Upstream made some significant changes including completely rewriting
the build system from autotools to meson.
I've also made some significant changes around pam_limits and when we
override limits set by systemd (now, we normally do not).
I'd love testing of
Hello,
Sam Hartman, le lun. 20 janv. 2025 13:21:32 -0700, a ecrit:
> I will admit I was kind of disappointed that rather than working to make
> my package handle arbitrary hostnames, the patch simply introduced an
> arbitrary constant for HURD.
It should not have, indeed.
> * Having different li
TL;DR: Is it time for the rest of Debian to stop conforming to HURD's
lack of maximums for path and hostname? By thispoint I think we
recognize those lack of maximums as an anti-pattern for DOS prevention
and other security reasons.
back in the day when I got my first HURD compatibility patch, I
On Sunday, January 19, 2025 9:47:19 AM MST Fabian Grünbichler wrote:
> On Sun, Jan 19, 2025, at 4:40 PM, Andrey Rakhmatullin wrote:
> > On Mon, Jan 20, 2025 at 02:02:51AM +1100, Russell Coker wrote:
> >> How do I specify an override file that works for this? When I have a file
> >> debian/source/l
* Phil Wyett [2025-01-20 17:18]:
I mainly ran into issue with autopkgtest which looked for --arch (unshare
default config) and failed unless I generated the arm64 chroot.
sbuild passes --arch to autopkgtest as you can't run tests in a cross
compile setup. autopkgtest then uses qemu to run the
On Mon, 2025-01-20 at 18:23 +0100, Jochen Sprickerhof wrote:
> * Phil Wyett [2025-01-20 17:10]:
> > * A VM with Debian trixie install - standard utilities plus ssh server.
>
> Which arch has the VM?
>
> > For --host=arm64 I have to generate an arm64 chroot and install crossbuild-
> > essential-a
* Phil Wyett [2025-01-20 17:10]:
* A VM with Debian trixie install - standard utilities plus ssh server.
Which arch has the VM?
For --host=arm64 I have to generate an arm64 chroot and install crossbuild-
essential-arm64 for crossbuilds to work.
If you want to cross build a package, i.e. yo
On Mon, Jan 20, 2025 at 05:18:01PM +, Phil Wyett wrote:
> I mainly ran into issue with autopkgtest
Good.
autopkgtest and package building are separate unrelated activities.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Jan 20, 2025 at 05:10:35PM +, Phil Wyett wrote:
> * A VM with Debian trixie install - standard utilities plus ssh server.
> * sbuild, pbuilder, piuparts and reprotest etc. installed.
> * qemu is not the install.
>
> For --host=arm64 I have to generate an arm64 chroot
No.
> and instal
On Mon, 2025-01-20 at 17:10 +, Phil Wyett wrote:
> On Mon, 2025-01-20 at 17:53 +0100, Jochen Sprickerhof wrote:
> > Hi Phil,
> >
> > * Phil Wyett [2025-01-20 16:35]:
> > > https://wiki.debian.org/sbuild
> > >
> > > https://wiki.debian.org/sbuild#Cross-compiling_packages
> > >
> > >
> > > O
On Mon, 2025-01-20 at 17:53 +0100, Jochen Sprickerhof wrote:
> Hi Phil,
>
> * Phil Wyett [2025-01-20 16:35]:
> > https://wiki.debian.org/sbuild
> >
> > https://wiki.debian.org/sbuild#Cross-compiling_packages
> >
> >
> > On the sbuild wiki page in the cross compiling section should we be
> > ad
Hi,
While discussing git-buildpackage use, various DEP-14 branches,
pristine-tar purpose, how to correctly filter/repackage upstream
tarballs in past 6 months I noticed that many people have
misconceptions of what is the purpose of the various branches and how
git merges across them are supposed t
On Mon, Jan 20, 2025 at 04:35:12PM +, Phil Wyett wrote:
> https://wiki.debian.org/sbuild
>
> https://wiki.debian.org/sbuild#Cross-compiling_packages
>
>
> On the sbuild wiki page in the cross compiling section should we be advising
> users that they need to create a chroot for the {ARCH} the
Hi Phil,
* Phil Wyett [2025-01-20 16:35]:
https://wiki.debian.org/sbuild
https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising
users that they need to create a chroot for the {ARCH} they wish to cross build
for an
Hi all,
https://wiki.debian.org/sbuild
https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising
users that they need to create a chroot for the {ARCH} they wish to cross build
for and also have the relevant crossbuild-e
Quoting Simon McVittie (2025-01-17 10:19:47)
> Many libraries have their API reference as HTML or even PDF, generated
> via something like Doxygen, gtk-doc or Pandoc,
Those packages currently using pandoc are recommended to check if either
of the much lighter cmark or cmark-gfm is sufficient.
-
22 matches
Mail list logo
