Ubuntu
gosu package

gosu 1.10-1ubuntu0.20.04.2 source package in Ubuntu

Changelog

gosu (1.10-1ubuntu0.20.04.2) focal-security; urgency=medium

  * No-change rebuild due to golang-1.13 update

 -- David Fernandez Gonzalez <email address hidden>  Tue, 11 Oct 2022 03:25:55 +0200

Upload details

Uploaded by:
David Fernandez Gonzalez
Uploaded to:
Focal
Original maintainer:
Ubuntu Developers
Architectures:
linux-any
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal updates universe misc
Focal security universe misc

Downloads

File Size SHA-256 Checksum
gosu_1.10.orig.tar.gz 17.3 KiB bcbe8ada8c435a253b1fa438f505dd311832a88f52316fd7d30342b106a4242c
gosu_1.10-1ubuntu0.20.04.2.debian.tar.xz 3.0 KiB c04e17d96e34de4493ce5111e70a4b3cf269e6cdfbd85c8b182eb6ad7ed0da0b
gosu_1.10-1ubuntu0.20.04.2.dsc 2.1 KiB ecb7f5511576ccd1b5f0f2abfaf8ea3ff6aa48fa5a7f90fc8a156528e2ea0b6a

View changes file

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.