Fedora EPEL 6 updates-testing report
by updates@fedoraproject.org
The following Fedora EPEL 6 Security updates need testing:
Age URL
64 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-dd6e4a3f0b python34-3.4.8-1.el6
12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1ceee884b4 prosody-0.10.2-1.el6
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-029b32bcf4 singularity-2.5.1-1.el6
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c unrtf-0.21.9-8.el6
The following builds have been pushed to Fedora EPEL 6 updates-testing
fedfind-4.2.0-1.el6
golang-1.9.7-1.el6
nsd-4.1.22-1.el6
python-requests-oauthlib-0.4.0-8.el6
rho-0.0.34-1.el6
Details about builds:
================================================================================
fedfind-4.2.0-1.el6 (FEDORA-EPEL-2018-093df42df8)
Fedora compose and image finder
--------------------------------------------------------------------------------
Update Information:
This new version of fedfind adds support for several new compose types: updates
and updates-testing composes, 'Container' nightly composes (which are like
'Docker' nightly composes but with a more generic name), and 'IoT' nightly
composes.
--------------------------------------------------------------------------------
ChangeLog:
* Tue Jun 5 2018 Adam Williamson <awilliam(a)redhat.com> - 4.2.0-1
- New release 4.2.0: support several new compose types
--------------------------------------------------------------------------------
================================================================================
golang-1.9.7-1.el6 (FEDORA-EPEL-2018-505b0fa758)
The Go Programming Language
--------------------------------------------------------------------------------
Update Information:
Rebase to 1.9.7
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jun 11 2018 Jakub ��ajka <jcajka(a)redhat.com> - 1.9.7-1
- Rebase to 1.9.7
--------------------------------------------------------------------------------
================================================================================
nsd-4.1.22-1.el6 (FEDORA-EPEL-2018-36ff992c9b)
Fast and lean authoritative DNS Name Server
--------------------------------------------------------------------------------
Update Information:
Update to 4.1.22 and enable round-robin, minimal-responses and refuse-any
--------------------------------------------------------------------------------
ChangeLog:
* Tue Jun 12 2018 Paul Wouters <pwouters(a)redhat.com> - 4.1.22-1
- Resolves rhbz#1575608 nsd 4.1.22 is available
- Enable round-robin, minimal-responses and refuse-any in nsd.conf
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1575608 - nsd-4.1.22 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1575608
--------------------------------------------------------------------------------
================================================================================
python-requests-oauthlib-0.4.0-8.el6 (FEDORA-EPEL-2018-aa53294840)
OAuthlib authentication support for Requests.
--------------------------------------------------------------------------------
Update Information:
This update just makes the package provide `python2-requests-oauthlib`, for
convenience and guideline compliance when building across Fedora and EPEL.
--------------------------------------------------------------------------------
ChangeLog:
* Tue Jun 12 2018 Adam Williamson <awilliam(a)redhat.com> - 0.4.0-8
- Add python2-requests-oauthlib provide
--------------------------------------------------------------------------------
================================================================================
rho-0.0.34-1.el6 (FEDORA-EPEL-2018-e4a95c36e5)
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 ```
--------------------------------------------------------------------------------
ChangeLog:
* Mon May 28 2018 Christopher Hambridge <chambrid(a)redhat.com> 0.0.34-1
- Update Python 2 dependency for EPEL support
- Bug fix for unicode processing (mdvickst(a)redhat.com)
- Bug fix for rpm output to /dev/null (mdvickst(a)redhat.com)
* Thu Apr 19 2018 Iryna Shcherbina <shcherbina.iryna(a)gmail.com> - 0.0.33-2
- Update Python 2 dependency declarations to new packaging standards
(See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
--------------------------------------------------------------------------------