Ubuntu
gosu package

gosu 1.17-1 source package in Ubuntu

Changelog

gosu (1.17-1) unstable; urgency=medium

  [ Debian Janitor ]
  * Remove constraints unnecessary since buster:
    + Build-Depends: Drop versioned constraint on dh-golang.
  * Change priority extra to priority optional.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
    Repository-Browse.
  * Update standards version to 4.6.0, no changes needed.

  [ Tianon Gravi ]
  * Update d/copyright to reflect upstream Apache-2.0 relicensing
    (https://github.com/tianon/gosu/issues/83)
  * Update to 1.17 upstream release
    - https://github.com/tianon/gosu/releases/tag/1.17
    - most notably, switching from "github.com/opencontainers/runc" to
      "github.com/moby/sys/user" (faithful, history-preserving lift-and-shift)

 -- Tianon Gravi <email address hidden>  Mon, 06 Nov 2023 03:26:46 -0800

Upload details

Uploaded by:
Debian Go Packaging Team
Uploaded to:
Sid
Original maintainer:
Debian Go Packaging Team
Architectures:
linux-any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
gosu_1.17-1.dsc 2.0 KiB 5bf61accfa300429fc57867024352154401a9809a612a54fc4cda91c3439c393
gosu_1.17.orig.tar.gz 14.9 KiB d984938705b81b90468a9f471adfdffeffaebd9deeac752d3e3a6060425b5d0d
gosu_1.17-1.debian.tar.xz 2.7 KiB 0dc7d651794038cac278a9ef1c39c6843faa53cc97b7017bbc4b5d611094c04e

No changes file available.

Binary packages built by this source

gosu: Simple Go-based setuid+setgid+setgroups+exec

 This is a simple tool grown out of the simple fact that "su" and "sudo" have
 very strange and often annoying TTY and signal-forwarding behavior. They're
 also somewhat complex to setup and use (especially in the case of "sudo"),
 which allows for a great deal of expressivity, but falls flat if all you need
 is "run this specific application as this specific user and get out of the
 pipeline".
 .
 The core of how "gosu" works is stolen directly from how Docker/libcontainer
 itself starts an application inside a container (and in fact, is using the
 "/etc/passwd" processing code directly from libcontainer's codebase).
 .
 Once the user/group is processed, we switch to that user, then we "exec" the
 specified process and "gosu" itself is no longer resident or involved in the
 process lifecycle at all. This avoids all the issues of signal passing and TTY,
 and punts them to the process invoking "gosu" and the process being invoked by
 "gosu", where they belong.