command-line-murders/i-0233d976c6d24ff77
by SadServersMore by SadServers
HTTP/1.1 200 OK < Server: Werkzeug/2.3.7 Python/3.9.2 Server: Werkzeug/2.3.7 Python/3.9.2 < Date: Sun, 31 Dec 2023 17:57:48 GMT Date: Sun, 31 Dec 2023 17:57:48 GMT < Content-Type: text/html; charset=utf-8 Content-Type: text/html; charset=utf-8 < Content-Length: 12 Content-Length: 12 < Connection: close Connection: close < * Closing connection 0 Unauthorizedadmin@i-0aea4ea4fa670d67d:~$ curl -localhost:5000
paris/i-0aea4ea4fa670d67d 00:26
by SadServersadmin@i-05ac26ae064999ace:~$ curl -vv^Cocalhost:5000 admin@i-05ac26ae064999ace:~$ ls -la total 44 drwxr-xr-x 6 admin admin 4096 Sep 24 2023 . drwxr-xr-x 3 root root 4096 Sep 17 2023 .. drwx------ 3 admin admin 4096 Sep 20 2023 .ansible -rw------- 1 admin admin 607 Mar 11 09:34 .bash_history -rw-r--r-- 1 admin admin 220 Aug 4 2021 .bash_logout -rw-r--r-- 1 admin admin 3526 Aug 4 2021 .bashrc drwxr-xr-x 4 admin admin 4096 Mar 11 09:31 .config -rw-r--r-- 1 admin admin 807 Aug 4 2021 .profile drwx------ 2 admin admin 4096 Sep 17 2023 .ssh drwxr-xr-x 2 admin root 4096 Sep 24 2023 agent -rwxrwx--- 1 root root 360 Sep 24 2023 webserver.py admin@i-05ac26ae064999ace:~$
paris/i-05ac26ae064999ace 05:04
by SadServersfsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme2n1p1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> admin@i-0eacfe699faffbd49:~$