{"update": {"autokarma": true, "autotime": true, "stable_karma": 3, "stable_days": 7, "unstable_karma": -3, "require_bugs": true, "require_testcases": true, "display_name": "", "notes": "# UnrealIRCd 6.1.0\nThis is UnrealIRCd 6.1.0 stable. It is the direct successor to 6.0.7, there will be no 6.0.8.\n\nThis release contains several channel mode `+f` enhancements and introduces a new channel mode `+F` which works with flood profiles like `+F normal` and `+F strict`. It is much easier for users than the scary looking mode `+f`.\n\nUnrealIRCd 6.1.0 also contains lots of JSON-RPC improvements, which is used by the [UnrealIRCd admin panel](https://www.unrealircd.org/docs/UnrealIRCd_webpanel). Live streaming of logs has been added and the webpanel now communicates to UnrealIRCd which web user issued a command (e.g.: who issued a kill, who changed a channel mode, ..).\n\nOther improvements are whowasdb (persistent `WHOWAS` history) and a new guide on running a Tor Onion service. The release also fixes a crash bug related to remote includes and fixes multiple memory leaks.\n\n## Enhancements\n* Channel flood protection improvements:\n  * New [channel mode `+F`](https://www.unrealircd.org/docs/Channel_anti-flood_settings) (uppercase F). This allows the user to choose a \"flood profile\", which (behind the scenes) translates to something similar to an `+f` mode. This so end-users can simply choose an `+F` profile without having to learn the complex channel mode `+f`.\n    * For example `+F normal` effectively results in `[7c#C15,30j#R10,10k#K15,40m#M10,8n#N15]:15`\n    * Multiple profiles are available and changing them is possible, see [the documentation](https://www.unrealircd.org/docs/Channel_anti-flood_settings).\n    * Any settings in mode `+f` will override the ones of the `+F` profile. To see the effective flood settings, use `MODE #channel F`.\n  * You can optionally set a default profile via [`set::anti-flood::channel::default-profile`](https://www.unrealircd.org/docs/Channel_anti-flood_settings#Default_profile). This profile is used if the channel is `-F`. If the user does not want channel flood protection then they have to use an explicit `+F off`.\n  * When channel mode `+f` or `+F` detect that a flood is caused by >75% of [\"unknown-users\"](https://www.unrealircd.org/docs/Security-group_block), the server will now set a temporary ban on `~security-group:unknown-users`. It will still set `+i` and other modes if the flood keeps on going (e.g. is caused by known-users).\n  * Forced nick changes (e.g. by NickServ) are no longer counted in nick flood for channel mode `+f`/`+F`.\n  * When a server splits on the network, UnrealIRCd now temporarily disables `+f`/`+F` join-flood protection for 75 seconds ([`set::anti-flood::channel::split-delay`](https://www.unrealircd.org/docs/Channel_anti-flood_settings#config)). This because a server splitting could mean that server has network problems or has died (or restarted), in which case the clients would typically reconnect to the remaining other servers, triggering an `+f`/`+F` join-flood and channels ending up being `+i` and such. That is not good because UnrealIRCd wants `+f`/`+F` to be as effortless as possible, with as little false positives as possible.\n    * If your network has 5+ servers and the user load is spread evenly among them, then you could disable this feature by setting the amount of seconds to `0`. This because in such a scenario only 1/5th (20%) of the users would reconnect and hopefully don't trigger `+f`/`+F` join floods.\n  * All these features only work properly if all servers are on 6.1.0-rc1 or later.\n* New module `whowasdb` (persistent `WHOWAS` history): this saves the `WHOWAS` history on disk periodically and when UnrealIRCd terminates, so next server boot still has the `WHOWAS` history. This module is currently not loaded by default.\n* New option [`listen::spoof-ip`](https://www.unrealircd.org/docs/Listen_block#spoof-ip), only valid when using UNIX domain sockets (so `listen::file`). This way you can override the IP address that users come online with when they use the socket (default was and still is `127.0.0.1`).\n* Add a new guide [Running Tor Onion service with UnrealIRCd](https://www.unrealircd.org/docs/Running_Tor_Onion_service_with_UnrealIRCd) which uses the new `listen::spoof-ip` and optionally requires a services account.\n* [JSON-RPC](https://www.unrealircd.org/docs/JSON-RPC):\n  * Logging of JSON-RPC requests (e.g. via snomask `+R`) has been improved, it now shows:\n    * The issuer, such as the user logged in to the admin panel (if known)\n    * The parameters of the request\n  * The JSON-RPC calls [`channel.list`](https://www.unrealircd.org/docs/JSON-RPC:Channel#channel.list), [`channel.get`](https://www.unrealircd.org/docs/JSON-RPC:Channel#channel.get), [`user.list`](https://www.unrealircd.org/docs/JSON-RPC:User#user.list) and [`user.get`](https://www.unrealircd.org/docs/JSON-RPC:User#user.get) now support an optional argument `object_detail_level` which specifies how detailed the [Channel](https://www.unrealircd.org/docs/JSON-RPC:Channel#Structure_of_a_channel) and [User](https://www.unrealircd.org/docs/JSON-RPC:User#Structure_of_a_client_object) response object will be. Especially useful if you don't need all the details in the list calls.\n  * New JSON-RPC methods [`log.subscribe`](https://www.unrealircd.org/docs/JSON-RPC:Log#log.subscribe) and [`log.unsubscribe`](https://www.unrealircd.org/docs/JSON-RPC:Log#log.unsubscribe) to allow real-time streaming of [JSON log events](https://www.unrealircd.org/docs/JSON_logging).\n  * New JSON-RPC method [`rpc.set_issuer`](https://www.unrealircd.org/docs/JSON-RPC:Rpc#rpc.set_issuer) to indiciate who is actually issuing the requests. The admin panel uses this to communicate who is logged in to the panel so this info can be used in logging.\n  * New JSON-RPC methods [`rpc.add_timer`](https://www.unrealircd.org/docs/JSON-RPC:Rpc#rpc.add_timer) and [`rpc.del_timer`](https://www.unrealircd.org/docs/JSON-RPC:Rpc#rpc.del_timer) so you can schedule JSON-RPC calls, like stats.get, to be executed every xyz msec.\n  * New JSON-RPC method [`whowas.get`](https://www.unrealircd.org/docs/JSON-RPC:Whowas#whowas.get) to fetch `WHOWAS` history.\n  * Low ASCII is no longer filtered out in strings in JSON-RPC, only in JSON logging.\n* A new message tag `unrealircd.org/issued-by` which is IRCOp-only (and used intra-server) to communicate who actually issued a command. See [docs](https://www.unrealircd.org/issued-by).\n\n## Changes\n* 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.\n* The [blacklist-module](https://www.unrealircd.org/docs/Blacklist-module_directive) directive now accepts wildcards, e.g. `blacklist-module rpc/*;`\n* The setting set::modef-boot-delay has been moved to [`set::anti-flood::channel::boot-delay`](https://www.unrealircd.org/docs/Channel_anti-flood_settings#config).\n* UnrealIRCd now only exempts `127.0.0.1` and `::1` from banning by default (hardcoded in the source). Previously UnrealIRCd exempted whole `127.*` but that gets in the way if you want to allow Tor with a [require authentication](https://www.unrealircd.org/docs/Require_authentication_block) block or soft-ban. Now you can just tell Tor to bind to `127.0.0.2` so its not affected by the default exemption.\n\n## Fixes\n* Crash if there is a parse error in an included file and there are other remote included files still being downloaded.\n* Memory leak in `WHOWAS`\n* Memory leak when connecting to a TLS server fails\n* Workaround a bug in some websocket implementations where the `WSOP_PONG` frame is unmasked (now permitted).\n\n## Developers and protocol\n* The `cmode.free_param` definition changed. It now has an extra argument `int soft` and for return value you will normally `return 0` here. You can `return 1` if you resist freeing, which is rare and only used by `+F` with set::anti-flood::channel::default-profile.\n* New `cmode.flood_type_action` which can be used to indicate a channel mode can be used from +f/+F as an action. You need to specify for which flood type your mode is, e.g. `cmode.flood_type_action = 'j';` for joinflood.\n* JSON-RPC supports [UNIX domain sockets](https://www.unrealircd.org/docs/JSON-RPC:Technical_documentation#UNIX_domain_socket) for making RPC calls. If this is used, UnrealIRCd now splits on `\\n` (newline) so multiple parallel requests can be handled properly.\n* Message tag `unrealircd.org/issued-by`, sent to IRCOps only. See [docs](https://www.unrealircd.org/issued-by).", "type": "enhancement", "status": "stable", "request": null, "severity": "medium", "suggest": "unspecified", "locked": false, "pushed": true, "critpath": false, "critpath_groups": "", "close_bugs": true, "date_submitted": "2023-05-06 21:47:17", "date_modified": "2023-05-06 21:50:40", "date_approved": "2023-05-14 01:41:59", "date_testing": "2023-05-07 01:39:37", "date_stable": "2023-05-15 02:12:03", "alias": "FEDORA-EPEL-2023-7665f08459", "test_gating_status": "ignored", "from_tag": null, "date_pushed": "2023-05-15 02:12:03", "meets_testing_requirements": true, "url": "https://bodhi.stg.fedoraproject.org/updates/FEDORA-EPEL-2023-7665f08459", "title": "unrealircd-6.1.0-1.el7", "version_hash": "d5d9c33e4479345c29bc5e2af13da4b40e3560d7", "release": {"name": "EPEL-7", "long_name": "Fedora EPEL 7", "version": "7", "id_prefix": "FEDORA-EPEL", "branch": "epel7", "dist_tag": "epel7", "stable_tag": "epel7", "testing_tag": "epel7-testing", "candidate_tag": "epel7-testing-candidate", "pending_signing_tag": "epel7-signing-pending", "pending_testing_tag": "epel7-testing-pending", "pending_stable_tag": "epel7-pending", "override_tag": "epel7-override", "mail_template": "fedora_epel_legacy_errata_template", "state": "archived", "composed_by_bodhi": true, "create_automatic_updates": false, "package_manager": "unspecified", "testing_repository": null, "released_on": null, "eol": null, "critpath_mandatory_days_in_testing": 14, "mandatory_days_in_testing": 7, "critpath_min_karma": 2, "min_karma": 1, "setting_status": null}, "user": {"name": "robert", "email": "redhat@linuxnetz.de", "id": 172, "avatar": "https://seccdn.libravatar.org/avatar/5ce2f7b6de1c95bdf5b1d0f117f568f9955a164c0916ea7552b5db21bf3e689a?s=24&d=retro", "openid": "robert.id.stg.fedoraproject.org", "groups": [{"name": "proventesters"}, {"name": "provenpackager"}, {"name": "packager"}, {"name": "ipausers"}, {"name": "ambassadors"}, {"name": "campusambassadors"}, {"name": "gitfedora-web"}, {"name": "fedora-contributor"}, {"name": "advocates"}, {"name": "fedorabugs"}, {"name": "gitsecurity-spin"}, {"name": "signed_fpca"}, {"name": "gitfama"}, {"name": "epel-packagers-sig"}, {"name": "web"}, {"name": "clamav"}, {"name": "trust admins"}]}, "comments": [{"karma": 0, "karma_critpath": 0, "text": "This update has been submitted for testing by robert. ", "timestamp": "2023-05-06 21:47:17", "update_id": 509021, "user_id": 91, "id": 3014428, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update's test gating status has been changed to 'ignored'.", "timestamp": "2023-05-06 21:47:18", "update_id": 509021, "user_id": 91, "id": 3014429, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "robert edited this update.", "timestamp": "2023-05-06 21:49:27", "update_id": 509021, "user_id": 91, "id": 3014436, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "robert edited this update.", "timestamp": "2023-05-06 21:50:40", "update_id": 509021, "user_id": 91, "id": 3014439, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been pushed to testing.", "timestamp": "2023-05-07 01:40:10", "update_id": 509021, "user_id": 91, "id": 3014558, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been submitted for stable by bodhi. ", "timestamp": "2023-05-14 01:41:59", "update_id": 509021, "user_id": 91, "id": 3022240, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been pushed to stable.", "timestamp": "2023-05-15 02:12:32", "update_id": 509021, "user_id": 91, "id": 3022776, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.stg.fedoraproject.org", "groups": []}}], "builds": [{"nvr": "unrealircd-6.1.0-1.el7", "signed": true, "release_id": 8, "type": "rpm", "epoch": 0}], "bugs": [], "updateid": "FEDORA-EPEL-2023-7665f08459", "karma": 0, "content_type": "rpm", "test_cases": []}, "can_edit": false, "ci_allowed": false}