Subj : Re: tqwCTF
To   : MeaTLoTioN
From : alterego
Date : Fri Apr 17 2020 08:22:00

  Re: Re: tqwCTF
  By: MeaTLoTioN to alterego on Thu Apr 16 2020 05:35 pm

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

Ahh, ok, got it.

 Me> Currently I have it set on a cronjob to kill and rebuild the container

You mean "restart" right? Shouldnt need to "build" it... My point earlier is
the "built container" has the app inside, and know when it is started, to
create (what ever it needs to create) to be unique from the last time it was
started.

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

There is a tool on github called dockersh - I did try to use it (about 2-3
years ago now), but couldnt at the time. But it should do what you need, but
you might need to tweak it.

On an incoming ssh connection, it should be able to spawn a container (and thus
 it does initialisation of uniqueness), connect the user to that instance, and
when they leave it kills it. Each incoming connection would get it's own
container.
....deon


.... All right, so I like spending money!  But name one other extravagance.
--- SBBSecho 3.10-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

.