

Going to IP directly could redirect to your first domain. This would trigger another request to your domain and could result in your logs.


Going to IP directly could redirect to your first domain. This would trigger another request to your domain and could result in your logs.
I also really hope my suggestions are just bullshit. Especially since those have the worst implications. But I would still be watching out for similar events. Just in case :)
I am not sure if this is a joke. Most commentators seem to perceive it this way. But just in case I will answer seriously.
This was done by a human:
I will expand on that last one since no one has done it: Do you have an issue with substance abuse? Do you have issues with your memory? Do you have any psychiatric issues? Your other personality could to this if you have a dissociative identity disorder. Check symptoms and pay attention on similar events. If this keeps happening go see a doctor.


This is built for privacy. Not sending any data to server. https://www.trustpdf.net/


deleted by creator
To setup kubernetes inside lxc you have to enable quite some capabilities inside host kernel and lxd containers that can be used to escalate privileges from beeing root in container to root in proxmox. Not completely sure but since even containerd containers share the same kernel, attacker might escalate directly from pod to proxmox host. But this last par I am not sure about.
I just recently tried to setup k3s in proxmox LXC containers. I had to do everything again after I learned it was not possible to make this setup without comproimising security and isolation. Now I run kubernetes inside virtual machines in proxmox.
In EU prisons look like schools. Seriously most prisons here just look like student dormitories. And nothing like movie (aka american) prisons.