responses sent early during request processing (primarily for
invalid requests) would display the username " " rater than "*"
in the controlpanel, in one case leading to user confusion
hooks returning exitcode 0 will:
* run the next hook, if any
* allow the original action, unless successive hook opposes
hooks returning exitcode 100 will:
* abort running successive hooks
* allow the original action
hooks returning anything other than 0 or 100 will:
* abort running successive hooks
* REJECT the original action
zmq can now respond with json; a dict with "rc", "rejectmsg",
"reloc" and so on, just like other hooks replying with json
context: if webworkers fail to initialize within 5sec,
up2k falls back to hashing on the main-thread instead
problem: if webworkers eventually do finish init,
they would then be racing the mainthread
fix: disconnect webworkers if init timeout
additionally, gradually extend the timeout as long as
the workers are still making progress initializing
if a textfile was shared with permission r below/inside a more
restrictive volume, then:
* if the parent volume had either permission g or h, then the files in
the parent folder could be accessed
* if the parent volume had anything stricter than g or h, then filenames
in the parent volume could be seen, but not accessed
introduce copyparty-en.pyz, affectionately known as companyparty.pyz
like copyparty-en.py, it is english-only but with a twist;
also remove smb support because the impacket references can look sus
in case a snakeoil salesman managed to convince your workplace into
purchasing their "internet security solution" which blocks downloads
of certain files according to file extensions -- or, in other words,
smoke and mirrors, with a comforting false sense of security