Subj : Re: tqwCTF
To   : alterego
From : MeaTLoTioN
Date : Thu Apr 16 2020 17:35:19

 al> So you shouldnt need to rebuild the image with a new challenge (although
 al> I dont really understand what you are trying to do).

No what I want it to be like is say you connect to my system on the right
port, it will create an instance of the container there and then in real
time, and assuming you log in with the right creds, it will land you inside
it at the shell. Once you log out, it will kill that instance.

The reason i would like it like that is so any changes, scripts, whatever
someone does when logged in, are all gone so that if someone else logs in
later, it's fresh ready for them to start that challenge without anything
being messed with.

Currently I have it set on a cronjob to kill and rebuild the container every
hour which does achieve sort of what I am wanting, but it would be nicer to
spawn a new instance upon connecting and despawn it when leaving.

 al> when you start the stack or service, so "docker stop" or "kill 1" (from

Hmm a "kill 1" from inside sounds reasonable-ish... I could make it do that
upon logout, so that when they log in again it will be fresh and not have to
restart it every hour... but if 2 people are logged in at the same time, and
one logs out, it will kill the progress of the other user... so hmm, not sure
how to proceed with this yet.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿
|07ÄÄ |08[|09fsx|08]  |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ
|07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08]  |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
 * Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (1337:1/101)

.