The following Fedora EPEL 6 Security updates need testing: Age URL 912 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 802 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb mcollective-2.8.4-1.el6 774 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9 thttpd-2.25b-24.el6 384 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3e50897ac libbsd-0.8.3-2.el6 114 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-4c76ddcc92 libmspack-0.6-0.1.alpha.el6 33 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6aaee32b7e optipng-0.7.6-6.el6 15 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6e4ce19598 monit-5.25.1-1.el6 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-37c8dbd6f1 gifsicle-1.90-1.el6 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8c9006d462 heimdal-7.5.0-1.el6 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-fde8252ab7 python-bottle-0.12.13-1.el6 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-752a7c9ad4 rootsh-1.5.3-17.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing bouncycastle-1.58-2.el6 canl-java-2.5.0-1.el6 ipmiutil-3.0.8-1.el6 jglobus-2.1.0-4.el6 recap-1.3.0-1.el6 rho-0.0.31-2.el6 rootsh-1.5.3-17.el6 voms-api-java-3.2.0-7.el6 voms-clients-java-3.0.7-6.el6 Details about builds: ================================================================================ bouncycastle-1.58-2.el6 (FEDORA-EPEL-2018-71db8f6f28) Bouncy Castle Cryptography APIs for Java -------------------------------------------------------------------------------- Update Information: Update bouncycastle - all subpackages now built from the same source package. Some are new in EPEL 6. Add canl-java and voms-clients-java to EPEL 6. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1233527 - bouncycastle-mail in EPEL 6 https://bugzilla.redhat.com/show_bug.cgi?id=1233527 -------------------------------------------------------------------------------- ================================================================================ canl-java-2.5.0-1.el6 (FEDORA-EPEL-2018-71db8f6f28) EMI Common Authentication library - bindings for Java -------------------------------------------------------------------------------- Update Information: Update bouncycastle - all subpackages now built from the same source package. Some are new in EPEL 6. Add canl-java and voms-clients-java to EPEL 6. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1233527 - bouncycastle-mail in EPEL 6 https://bugzilla.redhat.com/show_bug.cgi?id=1233527 -------------------------------------------------------------------------------- ================================================================================ ipmiutil-3.0.8-1.el6 (FEDORA-EPEL-2018-80a2dcca4c) Easy-to-use IPMI server management utilities -------------------------------------------------------------------------------- Update Information: update from upstream 3.0.8, RHBZ#1423055 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1423055 - ipmiutil-3.0.8 is available https://bugzilla.redhat.com/show_bug.cgi?id=1423055 [ 2 ] Bug #1531830 - Typo in %post scriptlet https://bugzilla.redhat.com/show_bug.cgi?id=1531830 -------------------------------------------------------------------------------- ================================================================================ jglobus-2.1.0-4.el6 (FEDORA-EPEL-2018-71db8f6f28) Globus Java client libraries -------------------------------------------------------------------------------- Update Information: Update bouncycastle - all subpackages now built from the same source package. Some are new in EPEL 6. Add canl-java and voms-clients-java to EPEL 6. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1233527 - bouncycastle-mail in EPEL 6 https://bugzilla.redhat.com/show_bug.cgi?id=1233527 -------------------------------------------------------------------------------- ================================================================================ recap-1.3.0-1.el6 (FEDORA-EPEL-2018-690bed5a7e) Generates reports of various system information -------------------------------------------------------------------------------- Update Information: - Latest upstream - Move config file from /etc/recap to /etc/recap.conf -------------------------------------------------------------------------------- References: [ 1 ] Bug #1525746 - recap-1.3.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1525746 -------------------------------------------------------------------------------- ================================================================================ rho-0.0.31-2.el6 (FEDORA-EPEL-2018-00a3356997) An SSH system profiler -------------------------------------------------------------------------------- Update Information: # Testing Rho To set up Rho, you create profiles that control how to run each scan. - Authentication profiles contain user credentials for a user with sufficient authority to complete the scan (for example, a root user or one with root-level access obtained through -sudo privilege escalation). - Network profiles contain network identifiers (for example, a hostname, IP address, or range of IP addresses) and the authentication profiles to be used for a scan. Complete the following steps, repeating them as necessary to access all parts of your environment that you want to scan: 1. Create at least one authentication profile with root-level access to Rho: ``` rho auth add --name auth_name --username root_name(--sshkeyfile key_file | --password) ``` a. At the Rho vault password prompt, create a new Rho vault password. This password is required to access the encrypted Rho data, such as authentication and network profiles, scan data, and other information. b. If you did not use the sshkeyfile option to provide an SSH key for the username value, enter the password of the user with root-level access at the connection password prompt. For example, for an authentication profile where the authentication profile name is roothost1, the user with root-level access is root, and the SSH key for the user is in the path ~/.ssh/id_rsa, you would enter the following command: ``` rho auth add --name roothost1 --username root --sshkeyfile ~/.ssh/id_rsa ``` You can also use the sudo-password option to create an authentication profile for a user with root-level access who requires a password to obtain this privilege. You can use the sudo-password option with either the sshkeyfile or the password option. For example, for an authentication profile where the authentication profile name is sudouser1, the user with root-level access is sysadmin, and the access is obtained through the password option, you would enter the following command: ``` rho auth add --name sudouser1 --username sysadmin --password --sudo-password ``` After you enter this command, you are prompted to enter two passwords. First, you would enter the connection password for the username user, and then you would enter the password for the sudo command. 2. Create at least one network profile that specifies one or more network identifiers, such as a host name, an IP address, a list of IP addresses, or an IP range, and one or more authentication profiles to be used for the scan: ``` rho profile add --name profile_name --hosts host_name_or_file --auth auth_name ``` For example, for a network profile where the name of the network profile is mynetwork, the network to be scanned is the 192.0.2.0/24 subnet, and the authentication profiles that are used to run the scan are roothost1 and roothost2, you would enter the following command: ``` rho profile add --name mynetwork --hosts 192.0.2.[1:254] --auth roothost1 roothost2 ``` You can also use a file to pass in the network identifiers. If you use a file to enter multiple network identifiers, such as multiple individual IP addresses, enter each on a single line. For example, for a network profile where the path to this file is /home/user1/hosts_file, you would enter the following command: ``` rho profile add --name mynetwork --hosts /home/user1/hosts_file --auth roothost1 roothost2 ``` # Running a scan Run the scan by using the scan command, specifying a network profile for the profile option and a location to store the output as a file in the comma-separated variables (CSV) format for the reportfile option: ``` rho scan --profile profile_name --reportfile filename.csv ``` For example, if you want to use the network profile mynetwork and save the report as mynetwork_scan1.csv, you would enter the following command: ``` rho scan --profile mynetwork --reportfile mynetwork_scan1.csv ``` ---- # Testing Rho To set up Rho, you create profiles that control how to run each scan. - Authentication profiles contain user credentials for a user with sufficient authority to complete the scan (for example, a root user or one with root-level access obtained through -sudo privilege escalation). - Network profiles contain network identifiers (for example, a hostname, IP address, or range of IP addresses) and the authentication profiles to be used for a scan. Complete the following steps, repeating them as necessary to access all parts of your environment that you want to scan: 1. Create at least one authentication profile with root-level access to Rho: ``` rho auth add --name auth_name --username root_name(--sshkeyfile key_file | --password) ``` a. At the Rho vault password prompt, create a new Rho vault password. This password is required to access the encrypted Rho data, such as authentication and network profiles, scan data, and other information. b. If you did not use the sshkeyfile option to provide an SSH key for the username value, enter the password of the user with root-level access at the connection password prompt. For example, for an authentication profile where the authentication profile name is roothost1, the user with root- level access is root, and the SSH key for the user is in the path ~/.ssh/id_rsa, you would enter the following command: ``` rho auth add --name roothost1 --username root --sshkeyfile ~/.ssh/id_rsa ``` You can also use the sudo- password option to create an authentication profile for a user with root-level access who requires a password to obtain this privilege. You can use the sudo- password option with either the sshkeyfile or the password option. For example, for an authentication profile where the authentication profile name is sudouser1, the user with root-level access is sysadmin, and the access is obtained through the password option, you would enter the following command: ``` rho auth add --name sudouser1 --username sysadmin --password --sudo-password ``` After you enter this command, you are prompted to enter two passwords. First, you would enter the connection password for the username user, and then you would enter the password for the sudo command. 2. Create at least one network profile that specifies one or more network identifiers, such as a host name, an IP address, a list of IP addresses, or an IP range, and one or more authentication profiles to be used for the scan: ``` rho profile add --name profile_name --hosts host_name_or_file --auth auth_name ``` For example, for a network profile where the name of the network profile is mynetwork, the network to be scanned is the 192.0.2.0/24 subnet, and the authentication profiles that are used to run the scan are roothost1 and roothost2, you would enter the following command: ``` rho profile add --name mynetwork --hosts 192.0.2.[1:254] --auth roothost1 roothost2 ``` You can also use a file to pass in the network identifiers. If you use a file to enter multiple network identifiers, such as multiple individual IP addresses, enter each on a single line. For example, for a network profile where the path to this file is /home/user1/hosts_file, you would enter the following command: ``` rho profile add --name mynetwork --hosts /home/user1/hosts_file --auth roothost1 roothost2 ``` # Running a scan Run the scan by using the scan command, specifying a network profile for the profile option and a location to store the output as a file in the comma-separated variables (CSV) format for the reportfile option: ``` rho scan --profile profile_name --reportfile filename.csv ``` For example, if you want to use the network profile mynetwork and save the report as mynetwork_scan1.csv, you would enter the following command: ``` rho scan --profile mynetwork --reportfile mynetwork_scan1.csv ``` -------------------------------------------------------------------------------- ================================================================================ rootsh-1.5.3-17.el6 (FEDORA-EPEL-2018-752a7c9ad4) Shell wrapper for auditing -------------------------------------------------------------------------------- Update Information: Fix permissions on rootsh log directory to limit it to root. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1526255 - rootsh log directory is world readable https://bugzilla.redhat.com/show_bug.cgi?id=1526255 -------------------------------------------------------------------------------- ================================================================================ voms-api-java-3.2.0-7.el6 (FEDORA-EPEL-2018-71db8f6f28) Virtual Organization Membership Service Java API -------------------------------------------------------------------------------- Update Information: Update bouncycastle - all subpackages now built from the same source package. Some are new in EPEL 6. Add canl-java and voms-clients-java to EPEL 6. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1233527 - bouncycastle-mail in EPEL 6 https://bugzilla.redhat.com/show_bug.cgi?id=1233527 -------------------------------------------------------------------------------- ================================================================================ voms-clients-java-3.0.7-6.el6 (FEDORA-EPEL-2018-71db8f6f28) Virtual Organization Membership Service Java clients -------------------------------------------------------------------------------- Update Information: Update bouncycastle - all subpackages now built from the same source package. Some are new in EPEL 6. Add canl-java and voms-clients-java to EPEL 6. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1233527 - bouncycastle-mail in EPEL 6 https://bugzilla.redhat.com/show_bug.cgi?id=1233527 -------------------------------------------------------------------------------- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
