| module app | |
| go 1.21.4 | |
| replace k8s.io/client-go => k8s.io/client-go v0.28.3 | |
| require ( | |
| github.com/hobbyfarm/gargantua/v3 v3.0.1-rc0.0.20231024152032-eabf2ecf99b4 // Master Branch | |
| k8s.io/apimachinery v0.28.3 | |
| k8s.io/client-go v12.0.0+incompatible |
| control 'cis-dil-benchmark-4.2.1.1' do | |
| title 'Ensure rsyslog Service is enabled' | |
| desc "Once the rsyslog package is installed it needs to be activated.\n\nRationale: If the rsyslog service is not activated the system may default to the syslogd service or lack logging instead." | |
| impact 1.0 | |
| tag cis: 'distribution-independent-linux:4.2.1.1' | |
| tag level: 1 | |
| only_if do | |
| package('rsyslog').installed? || command('rsyslogd').exist? |
This pull request creates a new resource FederatedRolePermissionsBoundary in LZConfig/templates/aws_baseline/aws-landing-zone-default-azure-roles.template
FederatedRolePermissionsBoundary is an IAM Policy that gets applied as a Permissions Boundary to all existing federated roles.
This policy has several statements:
AllowAll -- Allows all actions by default
DenyWriteToRoleWithoutBoundaryPolicy -- Denies the ability to write to any roles without this boundary policy attached
I hereby claim:
To claim this, I am signing this object:
| localhost inventory_variable=true ansible_connection=local |
| /* Tiny web server in Golang for sharing a folder | |
| Copyright (c) 2010 Alexis ROBERT <[email protected]> | |
| Contains some code from Golang's http.ServeFile method, and | |
| uses lighttpd's directory listing HTML template. */ | |
| package main | |
| import "http" | |
| import "io" |