| Age | Commit message (Collapse) | Author |
|---|
|
After `puppet-catalog-test` has been recently updated it failed
in our CI with:
File[/etc/apt/sources.list] has notify relationship to invalid
resource Exec[apt_updated]
See #8814 for more details.
Resolves: #8814
https://github.com/invadersmustdie/puppet-catalog-test/commit/ac386793c2c456d2071dd0adda716224128f0bb3
|
|
We moved from develop to master some time ago so
we should use master for CI testing as well.
|
|
|
|
|
|
|
|
|
|
Eth0 is vagrant's main interface to access the box
|
|
|
|
|
|
|
|
|
|
|
|
Without private networking, the box cannot get directly
accessed, only via port forwardings.
https://www.vagrantup.com/docs/networking/private_network.html
- Resolves: #7769
|
|
Virtualbox adds eth1 as second interface when private networking
is enabled.
- Related: #7769
|
|
closes #8414 as well
|
|
|
|
Depending whether couchdb is running on the same node as
nickserver, couchdb is available on localhost:
- When couchdb is running on a different node: Via stunnel, which is
bound to 4000.
- When couchdb is running on the same node: On port 5984
Resolves: #8793
|
|
|
|
|
|
|
|
We should include this in soledad-server package as
dependency but until we sorted out this, we depend
soledad-server on ssl-cert in the platform.
see https://0xacab.org/leap/soledad/issues/8849 for
|
|
|
|
Resolves: #8791
|
|
The newer version is needed for the single-hop functionality.
|
|
This makes a more clear site_tor::relay class that the leap service
includes, and a more generic site_tor class that other classes can
depend on for setting up the initial install.
|
|
|
|
|
|
Limit ci.leap.se deployment to leap/master (Closes #8782)
Closes #8782
See merge request !83
|
|
|
|
This gets us a simple apt repository privilege separation:
(a) our key can't be used to forge other repos
(b) other keys can't be used to forge our repo.
From sources.list(5):
ยท Signed-By (signed-by) is either an absolute path to a keyring
file (has to be accessible and readable for the _apt user, so ensure
everyone has read-permissions on the file) or one or more
fingerprints of keys either in the trusted.gpg keyring or in the
keyrings in the trusted.gpg.d/ directory (see apt-key
fingerprint). If the option is set, only the key(s) in this keyring
or only the keys with these fingerprints are used for the
apt-secure(8) verification of this repository. Defaults to the value
of the option with the same name if set in the previously acquired
Release file. Otherwise all keys in the trusted keyrings are
considered valid signers for this repository.
|
|
|
|
|
|
* Change environment names for clarity:
. Use staging for deploying to latest
. Use production environments to deploy to demo:
production/vpn
production/mail
* Install leap_cli if not present and define default values
* Remove old nodes from cached runs
* Remove no longer used SEEDS variable
* Debugging improvements:
. Hide secrets when calling ci-build.sh with xtrace enabled
. Use unbuffer to we can add debug output locally
. Add debugging to build_from_scratch()
|
|
|
|
Pull duplicated bits into a function
|
|
This cuts the number of hops for a tor onion service from 6 to 3,
speeding it up considerably. This removes the anonymity aspect of the
service, so it must be enabled intentionally, knowing that the server's
location no longer is hidden.
|
|
|
|
subrepo:
subdir: "puppet/modules/tor"
merged: "5ef29012"
upstream:
origin: "https://leap.se/git/puppet_tor"
branch: "master"
commit: "5ef29012"
git-subrepo:
version: "0.4.0"
origin: "https://github.com/ingydotnet/git-subrepo"
commit: "2e78d5d"
|
|
|
|
|
|
|
|
|
|
. Reorganize script to allow for multiple builds
. Add latest build, pulling from the ibex provider
. Run the build as the cirunner unprivileged user
. Set pipefail because job is run within a pipe
. Change name of 'build' stage to 'deploy'
. Setup an environment for the latest CI deployment
|
|
Add a `leap help` command at the end of the CI setup.sh to ensure that
the command is setup properly before continuing
|
|
|
|
This replaces the secret_token from rails 4.1 on.
Both are used for securing cookies in the browser. The secret_key_base
will also encrypt the cookies while the token will only sign them.
Keeping the token in there for now allows us to migrate existing sessions
/ cookies to the new secrets. We can remove it in the next version once
all providers have run with secret_key_base for a while.
|
|
|
|
|
|
|
|
|
