I started using Chrome Remote Desktop via https://remotedesktop.google.com/ recently.
I set up remote access to a number of computers in an office I'm supporting.
I'd like to promote it as a good way for others to access computers remotely as needed, but I'm concerned that I won't be able to monitor use effectively for potential abuse.
Does using Chrome Remote Desktop create logs or reports that could be used by a G Suite administrator to monitor use?
I'm looking for a table of CentOS versions and corresponding default password hash algorithms. Google searches didn't reveal any matches that look like they have all the information in one place.
Ubuntu publishes a table like the one I'm looking for on their wiki.
Until recently, I was under the impression that merely declaring a resource with various attributes would ensure that Puppet manages the resource and brings it back to the configured state if it were to change.
Today, I found that wasn't the case for a yumrepo resource I have configured, until I added an audit => all metaparameter to the resource. I deleted /etc/yum.repos.d/foo.repo and ran puppetd --test. Puppet did not recreate the resource. Does that indicate a Puppet defect?
If that's the intended behavior, it begs the question, what other resources require audit => all to tell Puppet to manage the resource's state if it changes on the system under management?
Here is the repository class:
class yum::therepo {
# Temporarily remove the Yum repo configuration if we don't have
# httpd yet.
exec { 'disable-the-repo-to-get-its-dependencies':
provider => shell,
command => 'rm -f /etc/yum.repos.d/the.repo',
unless => 'rpm -q httpd',
onlyif => 'test -f /etc/yum.repos.d/the.repo',
before => [Package['httpd'], Exec['httpd-for-yum'],],
path => '/bin:/usr/bin',
}
# Ensures httpd is running as a Yum server before anything else
# tries to install packages from it.
exec { 'httpd-for-yum':
provider => shell,
command => '/sbin/service nginx stop || true ; /sbin/service httpd restart',
require => Class['yum::server'],
}
yumrepo {
"the":
require => [Exec['httpd-for-yum'],],
descr => "The YUM Repo",
baseurl => "http://yum/repos/redhat/5/x86_64/",
gpgcheck => "0",
enabled => "1",
# One puppet run failed to recreate the.repo. I added audit
# => all, and the next puppet run did recreate the.repo.
# Possibly a red herring. I'd like to understand why it
# worked in one case and not in the other.
#audit => all,
}
}
And the Yum server class:
class yum::server {
include httpd
include iptables
package { ['createrepo']:
ensure => present;
}
exec { 'update-repo-metadata':
require => [ Package['createrepo']],
cwd => '/var/www/html/yum',
command => '/usr/bin/createrepo --update -d repos/redhat/5/x86_64/',
creates => '/var/www/html/yum/repos/redhat/5/x86_64/repodata/repomd.xml',
}
file {'/etc/httpd/conf.d/yum.conf':
ensure => file,
mode => 0644,
source => "puppet:///modules/yum/yum_httpd.conf",
require => Package['httpd'],
notify => Service['httpd'],
}
}
In my Puppet configuration I want to say "If I declare class X, apply its resources before class Y." In other words, I want to declare an ordering, but remain silent about whether or not to apply class X.
If I understand the "before" metaparameter correctly, saying:
class X {
...
before => Class['Y'],
}
class Y {
...
}
node N {
include Y
}
node M {
include X
include Y
}
will include X's and Y's resources on both nodes M and N. Instead, what I want is to express separately, "Apply just Y," or "Apply X and Y, and apply X before Y."
For context, what I want to do more concretely is to ensure that my Yum repositories are configured before Puppet applies package resources. I want to omit some repositories from some nodes. I want my package resource definitions to remain naive about the corresponding repositories; I don't want to litter my package resource definitions with dependencies on specific repositories.
I tried using Run Stages, but beyond the simplest configuration, they seem to cause dependency cycles. For example, this would work:
stage { 'first': before => Stage['main'] }
class X {
...
before => Class['Y'],
}
class Y {
...
}
node N {
include Y
}
node M {
class { "X": stage => first }
include Y
}
But this wouldn't:
stage { 'first': before => Stage['main'] }
class X {
...
class { "Z": stage => first } # to avoid Z "floating off"
before => Class['Y'],
}
class Y {
...
include Z
}
class Z { ... }
node N {
include Y
}
node M {
class { "X": stage => first }
include Y
}
In the latter, Puppet thinks there is a dependency cycle. I presume that's due to Z being declared and its resources being managed in two different stages. I could potentially simplify the classes I need in stage "first" to avoid the dependency cycle problems I'm seeing in practice, but the Puppet documentation spreads FUD about Run Stages.
Here's the specific bit of configuration that makes Run Stages really unappealing to me. In development VMs I'm bootstrapping a Yum server locally via a "devrepo".
class yum::devrepo {
# Ensures httpd is running as a Yum server before anything else
# tries to install packages from it.
exec { 'httpd-for-yum':
command => '/sbin/service httpd restart',
require => Class['yum::server'],
}
yumrepo {
"devrepo":
require => [Exec['httpd-for-yum'],],
descr => "Local Dev YUM Repo",
baseurl => "http://localhost/repos/redhat/5/x86_64/",
gpgcheck => "0",
enabled => "1",
}
}
class yum::server {
include httpd
package { ['createrepo']:
ensure => present;
}
exec { 'update-repo-metadata':
require => [ Package['createrepo']],
cwd => '/var/www/html/yum',
command => '/usr/bin/createrepo --update -d repos/redhat/5/x86_64/',
creates => '/var/www/html/yum/repos/redhat/5/x86_64/repodata/repomd.xml',
}
file {'/etc/httpd/conf.d/yum.conf':
ensure => file,
mode => 0644,
source => "puppet:///modules/yum/yum_httpd.conf",
require => Package['httpd'],
notify => Service['httpd'],
}
}
I want to include my production Yum repo on some nodes and the dev repo on others.
If I put yum::server and yum::devrepo in stage "first", then later httpd declarations in other classes cause problems later, because the other classes put httpd in the main stage.
If Puppet can express "If I declare class X, apply its resources before class Y", how? If not, how can I get the ordering I want without dependency cycles and without including Yum repository resources that I want to omit?