juju-core-1 1.25.6-0ubuntu1.16.04.2 source package in Ubuntu

Changelog

juju-core-1 (1.25.6-0ubuntu1.16.04.2) xenial-security; urgency=medium

  * SECURITY UPDATE: Privilege escalation via juju-run (LP: #1682411)
    - debian/patches/CVE-2017-9232.patch: create a unix domain socket with
      restricted permissions to limit juju-run to only similarly privileged
      processes.
    - CVE-2017-9232

 -- Seth Arnold <email address hidden>  Fri, 26 May 2017 15:29:18 -0700

Upload details

Uploaded by:
Seth Arnold on 2017-05-27
Uploaded to:
Xenial
Original maintainer:
Ubuntu Developers
Architectures:
any all
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial updates on 2017-06-03 universe devel
Xenial security on 2017-06-02 universe devel

Downloads

File Size SHA-256 Checksum
juju-core-1_1.25.6.orig.tar.gz 11.5 MiB 49baa5fc208c68cecb33ed12f4f697aba2a2ea87ab9c82aaf94afc88614935ab
juju-core-1_1.25.6-0ubuntu1.16.04.2.debian.tar.xz 19.4 KiB 590591a5dfa5a6ab3dd9c991e92d10b6ed7857ebfa47ef09c5deeb77410e3728
juju-core-1_1.25.6-0ubuntu1.16.04.2.dsc 1.9 KiB c46a08e52d6f10f050afbfbd2b1b983c34de9a6ad00bbb75b742173284a80d4f

View changes file

Binary packages built by this source

juju-1-default: Juju is devops distilled - client (legacy juju-1 symlink)

 Through the use of charms, juju provides you with shareable, re-usable,
 and repeatable expressions of devops best practices. You can use them
 unmodified, or easily change and connect them to fit your needs. Deploying
 a charm is similar to installing a package on Ubuntu: ask for it and
 it’s there, remove it and it’s completely gone.
 .
 This package contains a symlink for legacy juju-1 tooling that requires
 the /usr/bin/juju binary to point to juju-1, rather than juju-2.0.
 .
 No other packages should depend on this package.

juju-1.25: Juju is devops distilled - client

 Through the use of charms, juju provides you with shareable, re-usable,
 and repeatable expressions of devops best practices. You can use them
 unmodified, or easily change and connect them to fit your needs. Deploying
 a charm is similar to installing a package on Ubuntu: ask for it and
 it’s there, remove it and it’s completely gone.
 .
 This package provides the client application of creating and interacting
 with Juju environments.

juju-core: transitional package for supporting multiple Juju versions

 Dependency package providing the latest 1.25 stable version of Juju.

juju-local: dependency package for the Juju local provider

 Through the use of charms, juju provides you with shareable, re-usable,
 and repeatable expressions of devops best practices. You can use them
 unmodified, or easily change and connect them to fit your needs. Deploying
 a charm is similar to installing a package on Ubuntu: ask for it and
 it’s there, remove it and it’s completely gone.
 .
 This is a dependency package for those who want to use the Juju local
 provider, allowing Juju Charms to be tested locally using LXC containers.

juju-local-kvm: dependency package for the Juju local provider with KVM

 Through the use of charms, juju provides you with shareable, re-usable,
 and repeatable expressions of devops best practices. You can use them
 unmodified, or easily change and connect them to fit your needs. Deploying
 a charm is similar to installing a package on Ubuntu: ask for it and
 it’s there, remove it and it’s completely gone.
 .
 This is a dependency package for those who want to use the Juju local
 provider, allowing Juju Charms to be tested locally using KVM containers.