This $ENV:PATH holds the value of your current PATH settings. This variable can be updated in your current PowerShell terminal :
$ENV:PATH="$ENV:PATH;C:\Program Files (x86)\Notepad++"
You can also retrieve the current value with the following cmdlet Get-ItemProperty :
Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH
To make this change permanently, open up a new PowerShell terminal as Administrator (using runas) :
$oldpath = (Get-ItemProperty -Path ‘Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH).Path
$newpath = "$oldpath;C:\Program Files (x86)\Notepad++"
Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment’ -Name PATH -Value $newpath
Now, just log out of your current Windows session to take this change into account
NB : Tested successfully on Windows 10
yum-security is a plugin to the Red Hat Entreprise Linux package manager yum. It helps installing only security updates (RHSA) (as opposed to bug fixes (RHBA) or enhancements (RHEA)).
Explanation of RHSA, RHBA and RHEA advisories
RHEL 7 : yum-security is part of yum
RHEL 6 :
yum install yum-plugin-security
List all available erratas without installing them :
yum updateinfo list available
List all available security updates without installing them :
yum updateinfo list security all
yum updateinfo list sec
List of the currently installed security updates :
yum updateinfo list security installed
More examples are available in this Red Hat KB article
Red Hat has been provided security information since January 2005 through different ways :
RHSA-Announce mailing list, Red Hat CVE database and Red Hat Product Errata
For a better access of their data, the Red Hat Product Security has just released a beta API. It provides more search options for accessing real-time data.
More details can be found in the post below :
Red Hat Security Blog post about their new Security Data API service
RedHat Security Data API
Quick round up of the Spacewalk client configuration files :
The main configuration file is : /etc/sysconfig/rhn/rhncfg-client.conf
This file makes use of variables whose values are located in /etc/sysconfig/rhn/up2date
The server identity in Spacewalk is located in the XML file /etc/sysconfig/rhn/systemid
Two links for an in-depth explanation regarding Red Hat backporting security fixes process as well as compatibility between Red Hat security advisories and Mitre CVEs.
Backporting Security Fixes
Red Hat and CVE compatibility
Red Hat provides free access to two databases for errata and for CVE referenced in Red Hat products :
Red Hat Product Errata database
Red Hat CVE Database
Per Fail2ban main page, Fail2ban is the de facto tool to have to monitor malicious access attempts on your server and ban source IPs if need be.
The 2 presentations presents Fail2Ban’s history and features in a very-well manner :
Fail2Ban – Keep your boxes skiddie-free
Fail2ban : from personal to community-driven
Github’s project page
After a fresh installation of CentOS 7, your main network interface may be disabled. Its name may be enp0s3.
Check its status with :
nmcli dev status
To enable it permanently, look at its configuration file at /etc/sysconfig/network-scripts/ifcfg-enp0s3 and make the change from :
Restart the network service :
systemctl restart NetworkManager
The network interface status should now be as connected :
nmcli dev status