Variables are immutable by default. This makes Rust safer and makes concurrency easier.
Immutable means once a value is bound to that variable, it cannot be changed.
For example:
fn main() {
let x = 5;
session=lxqt | |
geometry=1920x1080 | |
localhost # comment this out to allow connections from anywhere | |
alwaysshared |
<!doctype html> | |
<html> | |
<head> | |
<meta name="viewport" content="width=device-width" /> | |
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> | |
<title>Simple Transactional Email</title> | |
<style> | |
/* ------------------------------------- | |
GLOBAL RESETS | |
------------------------------------- */ |
You can use these commands and rules to search for exploitation attempts against log4j RCE vulnerability CVE-2021-44228
This command searches for exploitation attempts in uncompressed files in folder /var/log
and all sub folders
sudo egrep -I -i -r '\$(\{|%7B)jndi:(ldap[s]?|rmi|dns|nis|iiop|corba|nds|http):/[^\n]+' /var/log
KEYMAPOPTS="us us" | |
HOSTNAMEOPTS="-n alpine" | |
INTERFACESOPTS="auto lo | |
iface lo inet loopback | |
auto eth0 | |
iface eth0 inet dhcp | |
hostname alpine | |
" | |
TIMEZONEOPTS="-z UTC" |
#!/bin/bash | |
sed -i -e 's/Anarchy/Arch/g' /etc/lsb-release | |
sed -i -e 's/Anarchy/Arch/g' /etc/os-release | |
sed -i -e 's/anarchy/arch/g' /etc/os-release | |
sed -i -e 's/arch-linux/www.archlinux/g' /etc/os-release | |
echo 'SUPPORT_URL="https://bbs.archlinux.org/"' >> /etc/os-release | |
echo 'BUG_REPORT_URL="https://bugs.archlinux.org/"' >> /etc/os-release | |
cp /etc/os-release /usr/lib/os-release | |
head -n -2 /etc/lightdm/lightdm-gtk-greeter.conf > lightdm-gtk-greeter.conf | |
mv lightdm-gtk-greeter.conf /etc/lightdm/ |
//////// | |
// The vm module lets you run a string containing javascript code 'in | |
// a sandbox', where you specify a context of global variables that | |
// exist for the duration of its execution. This works more or less | |
// well, and if you're in control of the code that's running, and you | |
// have a reasonable protocol in mind// for how it expects a certain | |
// context to exist and interacts with it --- like, maybe a plug-in | |
// API for a program, with some endpoints defined for it that do | |
// useful domain-specific things --- your life can go smoothly. |