* Is it possible to disable or make less verbose the log to syslog? It usually floods it and makes harder to follow up the other services. Even if I disable the HTTP_LOGGING in sbbs.ini, it still logs to the syslog.
* Is it possible to use ACLs to restict message areas for users accessing through web interface? For instance, I would like to make FidoNet only accesible from Telnet or SSH, not web.
Hi *.*,
I have two questions regarding the Synchronet web interface:
* Is it possible to disable or make less verbose the log to syslog? It usually floods it and makes harder to follow up the other services. Even if I disable the HTTP_LOGGING in sbbs.ini, it still logs to the syslog.
* Is it possible to use ACLs to restict message areas for users accessing through web interface? For instance, I would like to make FidoNet only accesible from Telnet or SSH, not web.
Do you have a LogLevel set in the [Web] section of sbbs.ini? If not, it's defaulting to whatever your global setting is (I think).
There is a "PROT" (protocl) ARS keyword: http://wiki.synchro.net/access:requirements
So you could set a message group or sub-board to have an Access Requirements of "PROT != HTTP AND PROT != HTTPS" for example.
You might be able to accomplish what you want by just restricting to authenticated users: "USER 1 AND !GUEST", as web users are unuathenticated (User 0) or Guest by default. That might be preferable.
Re: Two questions regarding web interfaceHTTP
By: Digital Man to Karloch on Mon Jan 14 2019 00:44:36
There is a "PROT" (protocl) ARS keyword: http://wiki.synchro.net/access:requirements
That was just what I was looking for! I missed that in the documentation.
So you could set a message group or sub-board to have an Access Requirements of "PROT != HTTP AND PROT != HTTPS" for example.
In my case for FidoNet area would be something like "!GUEST AND PROT !=
and PROT != HTTPS", but it looks like I run out of characters for the ARS key word. Is the designed behavior? Must I restrict to what fits in the string?
You might be able to accomplish what you want by just restricting to authenticated users: "USER 1 AND !GUEST", as web users are unuathenticated (User 0) or Guest by default. That might be preferable.
That would be another option, but R34 area discourages any kind of web gateway; I guess they have their point.
What I do not understand is the
"USER 1 AND !GUEST". By writting USER 1 am I not referencing the sysop?
Do you have a LogLevel set in the [Web] section of sbbs.ini? If not,
it's defaulting to whatever your global setting is (I think).
That made the trick. I didn't know I could set loglevel by service.
Quite useful! My log was flooded with web logging :)
The strings are limited in length, but there are plenty of shorthand reprenstations (e.g. "&" intead of "AND", "$U" instead of "USER") and you can remove the spaces.
I'm pretty sure they're referring to anonymous-web gateways (e.g. to keep the msgs out of the eyes of web crawling bots).
No. The default logic is "greater than or equal", so an ARS of "USER 1" is saying "user number greater than or equal to 1", thus excluding usernumber
0 (an unauthenticated user) from meeting the requirement.
i use methods like this to limit what i'm monitoring or looking for... the following are for following the logs live...
i use methods like this to limit what i'm monitoring or looking
for... the following are for following the logs live...
Valid ones indeed, but I want to avoid the file log growing too much
in a short time.
Decreasing web verbosity to 4 (warnings) is just what I was looking
for.
i'm glad you found a solution... me? i let logrotate handle archiving the file if it is larger than specified in the logrotate script... i just changed mine to retain 45 days (IIRC) of logs so i might have time to go back and look for possible problems and even trends in activities ;)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 89:49:17 |
Calls: | 6,496 |
Calls today: | 7 |
Files: | 12,100 |
Messages: | 5,277,556 |