Rconfig Installation
Dibe Naro
During the installation process ProcessWire needs write access, however, after you have installed PW, it is time to be more strict, and remove as much permission as you can on the server in question.
In the file /home/rconfig/www/lib/ajaxHandlers/ajaxArchiveFiles.php there is a blind command injection vulnerability in the ext parameter (different from CVE-2019-19509, which by the way, has not been resolved and it is still present, as you can see in the screenshot):
The first authentication bypass vulnerability lays on the register function of
/home/rconfig/www/lib/crud/userprocess.php. There is no authentication enforced, so we can just create our own admin user (ulevelid = 9).
The rconfig package provides various ways to override defaults, and instead of changing the active configuration (as in the config package), you can merge lists in order to arrive at a final configuration. These are very similar concepts, but not quite the same.
This looks very similar to what littler, getopt, and optparse are supposed to do. You are right. These packages offer amazing command line experience once you have a solid interface. In an iterative and evolving research and development situation, however, rconfig gives you agility.
Moreover, the rconfig package offers various ways for substituting environment variables, R global variables, and even substituting configuration values. The GetoptLong package has similar functionality but its focus is on command line interfaces and not configuration. Other tools, such as sprintf, glue, rprintf, and whiskers are aimed at substituting values from R expressions.
The installer has a Recover config.xml option which reads the configurationfile from an existing installation before starting the install process and putsit back in the exact same location when it finishes. This makes the featureuseful for upgrades, filesystem changes, or any other situation requiring areinstallation on the same disk. In addition to copying the existingconfiguration this function also attempts to copy the SSH host keys.
The recovery process attempts to repair the filesystem on the disk up to 10times, then mounts the disk and looks for the existing configuration file.If it is able to find and read the configuration file, the recovery processcopies it to a temporary RAM disk during the installation process.
As part of the installation routine, the installer checks for an existingconfiguration on a USB drive formatted as FAT or FAT32. If the installer canlocate and read a configuration file, it copies the file to the target disk.
The pfSense software memstick installation image contains a FAT partitionwhich the installer can use for this purpose. If the partition is not visibleon the workstation which wrote the memstick image, remove and reinsert theUSB drive.
This procedure is nearly identical to the method in Restore Configuration from USB During Install, butthe USB disk containing the configuration does not need to be present during theinstallation. The same warnings from that procedure also apply here.
USB drives which only contain files can be inserted before the firewallboots. Bootable USB drives, such as the installation memstick, should notbe inserted until after the firewall has started to boot from its own disk.This behavior will vary by target device and its boot preferences. Monitorthe console to find the appropriate timing.
This Metasploit module exploits an unauthenticated command injection vulnerability in rConfig versions 3.9.2 and prior. The install directory is not automatically removed after installation, allowing unauthenticated users to execute arbitrary commands via the ajaxServerSettingsChk.php file as the web server user. This module has been tested successfully on rConfig version 3.9.2 on CentOS 7.7.1908 (x64).
You can use a combination of INSTALL_K3S_EXEC, K3S_ environment variables, and command flags to pass configuration to the service configuration.The prefixed environment variables, INSTALL_K3S_EXEC value, and trailing shell arguments are all persisted into the service configuration.After installation, configuration may be altered by editing the environment file, editing the service configuration, or simply re-running the installer with new options.
As stated, the installation script is primarily concerned with configuring K3s to run as a service.
If you choose to not use the script, you can run K3s simply by downloading the binary from our release page, placing it on your path, and executing it. This is not particularly useful for permanent installations, but may be useful when performing quick tests that do not merit managing K3s as a system service.
If a key is specified in multiple config files, the values will get mergedtogether. Numbers, strings, and booleans will use the value in the deeperconfig directory taking precedence over ancestor directories, where thehome directory is the lowest priority. Arrays will be joined togetherwith higher precedence items being placed later in the merged array.
rconfig is a command line tool introduced in Oracle Database 10g R2 to convert Single-Instance 10g R2 Database to RAC(Real Application Cluster).
The other option is to use Convert to RAC option on the single-instance database target of Oracle Enterprise Manager Grid Control.
rconfig is located at $ORACLE_HOME/bin/.
rconfig takes in a xml input file and convert the Single Instance database whose information is provided in the xml.
A sample xml can be found $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC.xml.
Oracle 10g R2 Install has provided a sample rconfig input XML file called ConvertToRAC.xml under $ORACLE_HOME/assistants/rconfig/sampleXMLs. Make a copy of the sample XML file & make your own customised copy of input giving your Instance specific details. The Sample XML file includes comments to make understand how to edit each variable.
14. If unexpected server or other kind of error interrupts processing AFTER RMAN has already started to convert/copy files into ASM, prior to restarting rconfig, remove files that have been created in ASM or they will stay there and take up unnecessary space forever, and possibly cause rconfig to fail.
17. If issues with TEMP portion of rconfig, Select * from dba_temp_files. If any files returned indicate that they are not on ASM diskgroups, drop those files and add new tempfiles to match capacity of source environment.
To get started, you'll have to install the package. It's available on CRAN, so the installation can't be any simpler:
install.packages("config")
R config wants to read a config.yml file by default. You can change that by specifying a different value to the file parameter, but we'll stick to the convention today.
I did a fresh installation of Manjaro today, and the first thing I did was created two backups via Timeshift. The first backup is of a complete backup (system + home folder). The second backup is of the system only. I stored all this on the same HDD that Manjaro is running on.
08ab062aa8