Re: [dev][Quark] Big problem

2024-06-03 Thread Jeremy
Hi Fossy Dnmx, I'm re-opening this thread & I'm Hoping your health has returned. I want to say "cd ~; httpd" & then see everything in ~ from my Web Browser on port 8080. This is hard & I can't figure out all of these http servers recommended from suckless.org. "permission denied becuase of

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

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

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)

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

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

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

2023-02-26 Thread Thomas Oltmann
On Sun, Feb 26, 2023 at 3:53 PM wrote: > > 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. Ah i see.

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

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

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

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

2023-02-25 Thread Страхиња Радић
On 23/02/25 12:59PM, fo...@dnmx.org wrote: > Tried -s 128 -t 8, doesn't seem to do jack shit.. > Got less than 10 connection logs from Quark and then another dropped one.. > Is there any other reason Quark would print-out 'dropped', other than > connection pool at max? > > I restarted the jail,

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

2023-02-25 Thread fossy
Tried -s 128 -t 8, doesn't seem to do jack shit.. Got less than 10 connection logs from Quark and then another dropped one.. Is there any other reason Quark would print-out 'dropped', other than connection pool at max? I restarted the jail, so Quark's memory and stuff should have been reset.

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

2023-02-25 Thread fossy
Hey, I just read the quark.1 . I see the -s and -t options lol. I shall experiment.

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

2023-02-25 Thread fossy
Hi, Laslo. Sorry, I might not have been best at explaining problem, but then again - I didn't quite understand problem.. but said all I did understand. > one of my development goals for quark was to have no memory allocations at runtime. Right, I knew that.. but what about memory allocation

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

2023-02-25 Thread fossy
You are a brainless joke.

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

2023-02-25 Thread Hiltjo Posthuma
On Sat, Feb 25, 2023 at 09:50:42AM -0500, fo...@dnmx.org wrote: > Hello. > Before I start, I want to clarify 2 things: > 1. I'm not 100% sure if it's a Quark problem, but there are like 2/4th > chance that it is. > 2. I'm hosting my site over the Tor network > > Problem I have: software runs, can

[dev] [DEV][Quark] Big problem

2023-02-25 Thread fossy
Hello. Before I start, I want to clarify 2 things: 1. I'm not 100% sure if it's a Quark problem, but there are like 2/4th chance that it is. 2. I'm hosting my site over the Tor network Problem I have: software runs, can access it from localhost via curl, but cannot access it from Tor What