mkws also :P
mkws also :P
mkws, not pleased with the design tho, I'll keep it as close as possible to plain text tho as an homage to UNIX and tilde.institute which are an awesome group. I _personally_ believe all tiny scripts there are at least decent, I believe the linters are nice and the log analytics scripts are nice although, both of them may be rewritten in C even tho awk fits so well for the log analytics. And default.css is nice. I've incorporated the linters in my mkws build process.
mkws, not pleased with the design tho, I'll keep it as close as possible to plain text as an homage to UNIX and tilde.institute which are an awesome group. I _personally_ believe all tiny scripts there are at least decent, I believe the linters are nice and the log analytics scripts are nice although, both of them may be rewritten in C even tho awk fits so well for the log analytics. And default.css is nice. I've incorporated the linters in my mkws build process.
mkws, not pleased with the design tho, I'll keep it as close as possible to plain text as an homage to UNIX and tilde.institute which are an awesome group. I _personally_ believe all tiny scripts there are at least decent, I believe the linters are nice and the log analytics scripts are nice although, both of them may be rewritten in C even tho awk fits so well for the log analytics. And default.css is nice. I've incorporated the linters in my mkws build process.
mkws, not pleased with the design tho, I'll keep it as close as possible to plain text as an homage to UNIX and tilde.institute which are an awesome group. I _personally_ believe all tiny scripts there are at least decent, I believe the linters are nice and the log analytics scripts are nice although, both of them may be rewritten in C even tho awk fits so well for the log analytics. And default.css is nice. I've incorporated the linters in my mkws build process.
default.css is nice actually, some of the minimal class-less CSS inserts are not perhaps as minimal as they could be. Haven't had a chance to look over the others ones properly yet, but one thing I do really respect is the minimal and functional approach. I've played around with various web frameworks and tools, and like you I imagine, really just got sick of all the bloat and unnecessary complexity.
default.css is nice actually, some of the minimal class-less CSS inserts are not perhaps as minimal as they could be. Haven't had a chance to look over the others ones properly yet, but one thing I do really respect is the minimal and functional approach. I've played around with various web frameworks and tools, and like you I imagine, really just got sick of all the bloat and unnecessary complexity.
> I’ve played around with various web frameworks and tools, and like you I imagine, really just got sick of all the bloat and unnecessary complexity.
Exactly!
pp.
cl, cbl, fl, using pp.
cl, cbl, fl, using pp.
cl, cbl, fl, using pp.
pp. I believe this is a sane way to build dynamic website, parsing GET and POST variables in CGI is still a problem tho. I personally prefer interpreted languages for developing websites due to no compile time and in place debugging.
pp. I believe this is a sane way to build dynamic websites, parsing GET and POST variables in CGI is still a problem tho. I personally prefer interpreted languages for developing websites due to no compile time and in place debugging.
pp. I believe this is a sane way to build dynamic websites, parsing GET and POST variables in CGI is still a problem tho. I personally prefer interpreted languages for developing websites due to no compile time and in place debugging.
pp. I believe this is a sane way to build dynamic websites, parsing GET and POST variables in CGI is still a problem tho. I personally prefer interpreted languages for developing websites due to no compile time and in place debugging.
unshare ?
unshare ?
unshare ?
CGI pp and dump the variables in the global scope of the execve(3) sh. The security issue lays in overwriting any other variable already present in the global scope.
CGI pp and dump the variables in the global scope of the execve(3) sh. The security issue lays in overwriting any other variable already present in the global scope.
CGI pp and dump the variables in the global scope of the execve(3) sh. The security issue lays in overwriting any other variable already present in the global scope.
chroot is enough? thttpd supports chroot.
chroot is enough? thttpd supports chroot.
chroot is enough? thttpd supports chroot.
chroot only gives you an isolated root file system view. It does nothing to isolate the process or sandbox it, etc. I would use unshare + chroot.
chroot only gives you an isolated root file system view. It does nothing to isolate the process or sandbox it, etc. I would use unshare + chroot.
chroot only gives you an isolated root file system view. It does nothing to isolate the process or sandbox it, etc. I would use unshare + chroot.
unshare
unshare
unshare