1
1
Fork 0
mirror of https://github.com/ovh/the-bastion.git synced 2025-03-09 22:13:44 +08:00

bump to v3.00.02

This commit is contained in:
Stéphane Lesimple 2020-11-16 10:39:06 +00:00
parent a42c8fa12c
commit b87107dd23
No known key found for this signature in database
GPG key ID: 4B4A3289E9D35658
4 changed files with 21 additions and 6 deletions
README.md
doc
CHANGELOG.md
sphinx/installation
lib/perl/OVH

View file

@ -23,9 +23,11 @@ Please see the [online documentation](https://ovh.github.io/the-bastion/), or th
## TL;DR: disposable sandbox using Docker
This is a good way to test The Bastion within seconds, but [read the FAQ](https://ovh.github.io/the-bastion/faq.html#can-i-run-it-under-docker-in-production) if you're serious about using this in production.
This is a good way to test The Bastion within seconds, but [read the FAQ](https://ovh.github.io/the-bastion/faq.html#can-i-run-it-under-docker-in-production) if you're serious about using containerization in production.
OK, let's run the docker image:
The sandbox image is available for the following architectures: linux/386, linux/amd64, linux/arm/v6, linux/arm/v7, linux/arm64, linux/ppc64le, linux/s390x.
Let's run the docker image:
docker run -d -p 22 --name bastiontest ovhcom/the-bastion:sandbox
@ -60,7 +62,7 @@ Note that you can connect directly without using interactive mode, with:
bastion <remote_account_name>@<remote_machine_host_or_ip>
That's it! Additional documentation is available under the `doc/` folder and [online](https://ovh.github.io/the-bastion/).
That's it! Of course, there is a lot more to it, documentation is available under the `doc/` folder and [online](https://ovh.github.io/the-bastion/).
Be sure to check the help of the bastion (`bastion --help`) and the help of each osh plugin (`bastion --osh command --help`).
Also don't forget to customize your `bastion.conf` file, which can be found in `/etc/bastion/bastion.conf` (for Linux).
@ -73,12 +75,14 @@ Linux distros below are tested with each release, but as this is a security prod
- Ubuntu LTS 20.04, 18.04, 16.04, 14.04*
- OpenSUSE Leap 15.2*, 15.1*, 15.0*
*: Note that these versions have no MFA support.
*: Note that these versions have no out-of-the-box MFA support, as they lack packaged versions of `pamtester`, `pam-google-authenticator`, or both. Of course, you may compile those yourself.
Any other so-called "modern" Linux version are not tested with each release, but should work with no or minor adjustments.
The code is also known to work correctly under:
- FreeBSD 10+ / HardenedBSD [no MFA support]
- FreeBSD 10+ / HardenedBSD**
**: Note that FreeBSD has partial MFA support, due to its reduced set of available `pam` plugins. You can set it up to support an additional password or TOTP factor, but not both.
Other BSD variants partially work but are unsupported and discouraged as they have a severe limitation over the maximum number of supplementary groups (causing problems for group membership and restricted commands checks), no filesystem-level ACL support and missing MFA:

View file

@ -1,3 +1,9 @@
## v3.00.02 - 2020/11/16
- feat: add more archs to dockerhub sandbox
- fix: adminSudo: allow called plugins to read from stdin
- fix: add missing `echo` in the entrypoint of the sandbox
- chore: install-ttyrec.sh: adapt for multiarch
## v3.00.01 - 2020/11/06
- feat: add OpenSUSE 15.2 to the officially supported distros
- enh: install-ttyrec.sh: replaces build-and-install-ttyrec.sh, no longer builds in-place but prefers .deb and .rpm packages & falls back to precompiled static binaries otherwise

View file

@ -42,6 +42,11 @@ Note that this is done automatically for bastion admins.
Version-specific upgrade instructions
=====================================
v3.00.02
********
No specific upgrade instructions.
v3.00.01
********

View file

@ -5,7 +5,7 @@ use common::sense;
use Fcntl;
use POSIX qw(strftime);
our $VERSION = '3.00.01';
our $VERSION = '3.00.02';
BEGIN {
# only used by the handler below