Re: [dev][Quark] Big problem

2023-02-26 Thread fossy
By the way, are there connections being made to Quark that aren't logged, like some sort of silent handling? I am trying to come up with possible answer without reading code lol is fun. Like how does it drop connection after only 3 connections? I restarted the jail, which is like a computer restar

Re: [dev][Quark] Big problem - log file output

2023-02-26 Thread fossy
Alright, this is the log output, things were substituted, but important things should be there.. I deleted most of logs because it piled up.. The page attempts are a DDoS/access attack which I laugh at.. there were much dumber attempts lol.. I told them I got static sites, they search for php lol.

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
(replying to Laslo) > which is basically a CGI-interface and thus not within quark's scope. thttpd has a patch that adds basic CGI support, and I've quickly scanned the patch, and it seems super simple.. perhaps you could use that in one way or another. I don't mean to say "support intellectual pr

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
Hey, Laslo. Yeah, that's fine.. it's like "stable release" for normies. Ah. I kind-of like Quark.. I don't want to go try thttpd.. It does NOT work XD In fact - it seems to work much less.. like the opposite from before. I get like the IP (localhost) dropped - - usually it's IP (localhost) 200(o

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread Laslo Hunhold
On Sun, 26 Feb 2023 14:02:48 +0100 Thomas Oltmann wrote: Dear Thomas, > Looks to me like your version of quark is actually a lot newer than > 2020; Old versions of quark did not print that "dropped" message. > > Probably only tangentially related, > but I reported a bug in the connection droppi

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
If you guys want - perhaps we can play the printf game, or rather - the logging game?

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
Ah, I see. I forgot how to use git after such a long absence from programming.. +6 months. I ran the command and it's up to date, last commit is 68b4f733b2755762e43df90f73db5a6ec8d14104 on both of my sites. I see. I can test the patch, but I don't think I'm using AF_INET6 as I disabled IPv6 in Fr

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread Thomas Oltmann
, but I'm not 100% sure that this bug is responsible for your problem. To apply the patch, simply drop the .diff file in your quark source folder, then run git am quark-addr_cmp_fix-20230226.diff and then rebuild & reinstall with make make install From 0fc2f684e79795dcc4cbd

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
I did a git clone like it says on the main Quark web-site, and doing `mandoc -a quark.1` it shows '2020-09-27', and that's what I am using. Unless that's wrong and/or there's another way to get the version number - I'd like to know. > which meant that quark would likely drop legitimate connections

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread fossy
> Reread Laslo's message and look at the source code as he suggested in the mentioned message. I cannot afford that, I have health problems :(. Regardless - I am getting only ~5 requests per minute, and my biggest file is <3M, so even given the attack has a super-slow Tor circuit connection of say

Re: [dev] [DEV][Quark] Big problem

2023-02-26 Thread Thomas Oltmann
Hi fossy, Looks to me like your version of quark is actually a lot newer than 2020; Old versions of quark did not print that "dropped" message. Probably only tangentially related, but I reported a bug in the connection dropping code some time ago, which meant that quark would likely drop legitimat