| Update release notes a bit on JSON request logging and unrealircd.org/issued-by [skip ci] |
|
More...
|
almost 2 years ago
|
| Change RPC logging format for rpc.RPC_CALL: From: [rpc] Client RPC:adminpanel (Syzop): RPC call channel.set_mode: channel='#test', modes='+b', parameters='some!silly@ban' To: [rpc] RPC call channel.set_mode by RPC:adminpanel (Syzop): channel='#test', modes='+b', parameters='some!silly@ban' |
|
More...
|
almost 2 years ago
|
| Log parameters in rpc.RPC_CALL: [rpc] Client RPC:adminpanel (Syzop): RPC call channel.set_mode: channel='#test', modes='+b', parameters='some!silly@ban' |
|
More...
|
almost 2 years ago
|
| Logging: Log the issuer in rpc.RPC_CALL, when it is available. [rpc] Client RPC:adminpanel (Syzop): RPC call channel.set_mode |
|
More...
|
almost 2 years ago
|
| Get rid of unneeded buffer copying, if Jansson library >= v2.1 |
|
More...
|
almost 2 years ago
|
| For JSON-RPC with UNIX Domain sockets, split on \n (newline). This so multiple parallel requests can be handled properly. |
|
More...
|
almost 2 years ago
|
| Fix some warnings: change an int to time_t and vice-versa |
|
More...
|
almost 2 years ago
|
| Fix weird +F values when two channels merge. This was a forgotten TODO item for cmodef_dup_struct(), more netsync tests are still to follow. Bug reported by Lord255. |
|
More...
|
almost 2 years ago
|
| Fix crash on rpc-user { } block without a name. |
|
More...
|
almost 2 years ago
|
| Make channel.set_topic use the issuer internally. No logging or other changes yet, just unrealircd.org/issued-by testing. |
|
More...
|
almost 2 years ago
|
| RPC: add rpc.set_issuer, eg set to logged in user on the admin panel. This so UnrealIRCd knows who is issuing the commands. This information is then passed on to unrealircd.org/issued-by and is planned to be used by the logging system too. |
|
More...
|
almost 2 years ago
|
| Initial work on unrealircd.org/issued-by message tag. This will communicate the original issuer of a command. For example an "SAMODE #test +s" results in a SAMODE coming from :maintest.test.net MODE ....etc.... And with this feature, we will communicate the IRCOp who did it: @unrealircd.org/issued-by=OPER:Syzop..etc.... This tag is only sent to servers and to IRCOps, not to ordinary users. |
|
More...
|
almost 2 years ago
|
| Validate value of rpc-user THISNAME { } |
|
More...
|
almost 2 years ago
|
| Fix SAMODE showing tags for the person who executed the SAMODE instead of the server executing the MODE. Eg unrealircd.org/userhost was set. This occured because the client = &me; was done after the message tag preparation, now moved up so it's done before. |
|
More...
|
almost 2 years ago
|
| Add wildcard support to blacklist-module. This also removes the following warning as a side-effect: "blacklist-module for '%s' but module does not exist anyway". |
|
More...
|
almost 2 years ago
|
| Load RPC modules by default but don't enable webserver or RPC sockets. See release notes: +* The RPC modules are enabled by default now. This so remote RPC works + from other IRC servers for calls like `modules.list`. The default + configuration does not enable the webserver nor does it cause + listening on any socket for RPC, for that you need to follow the + [JSON-RPC](https://www.unrealircd.org/docs/JSON-RPC) instructions. |
|
More...
|
almost 2 years ago
|
| Update release notes [skip ci] |
|
More...
|
almost 2 years ago
|
| Fix dereferencing the wrong variable in a config_error() |
|
More...
|
almost 2 years ago
|
| Add and use set::modef-split-delay which makes +f ignore join-flood for this amount of seconds (default: 75) when a server splits. This helps in case a server dies and the clients reconnect to the other servers, causing a join-flood to be triggered needlessly. Of course, OTOH disabling a flood protection temporarily is not ideal, but after seeing it being triggered too often and requiring manual intervention in many +f/+F channels, this is the best option I think, if we want +f/+F to work as painless as possible. |
|
More...
|
almost 2 years ago
|
| Do some sanity checking on extban names: max 32 characters and a-z, 0-9, _, - |
|
More...
|
almost 2 years ago
|
| Do some sanity checks on flood profile names max length 24, and every character is a-z, 0-9, -, _ |
|
More...
|
almost 2 years ago
|
| Assume +f profile "normal" always exists, since that is the case. Also fix some "NULL check but dereferenced before" warnings. |
|
More...
|
almost 2 years ago
|
| Get rid of some shadow (bug in +f config profile handling) |
|
More...
|
almost 2 years ago
|
| Fix due to recent +f rewrite: add check for [ at start, fixes OOB read. |
|
More...
|
almost 2 years ago
|
| Update release notes [skip ci] |
|
More...
|
almost 2 years ago
|
| RPC: user.list and user.get now have optional object_detail_level. This is an integer which decides the amount of details in the response object. |
|
More...
|
almost 2 years ago
|
| Again a fix for JSON logging, so object_detail_level has same result as 6.0.6. |
|
More...
|
almost 2 years ago
|
| Fix JSON logging using the correct object_detail_level (same result as 6.0.6) |
|
More...
|
almost 2 years ago
|
| Bump rpc/channel module version to 1.0.5 [skip ci] |
|
More...
|
almost 2 years ago
|
| RPC: channel.get and channel.list now have optional object_detail_level. This is an integer which decides the amount of details in the response object. |
|
More...
|
almost 2 years ago
|
