neoirc

sneak/neoirc

Fork 0

Author	SHA1	Message	Date
sneak	d6a6296c1e	deploy (#189 ) check / check (push) Waiting to run Details Reviewed-on: #189	2026-10-22 18:52:00 +02:00
sneak	12a232ee1b	next → main: utility commands, IRC listener and audit fixes, build fixes (#111 ) check / check (push) Waiting to run Details Reviewed-on: #111	2026-10-22 18:27:05 +02:00
clawbot	d31fd529e2	Make an IRC listener connection follow its session's nick (closes #184 ) check / check (push) Canceled after 0s Details An IRC listener connection kept its own copy of its nick, so after the session's nick was changed from another client it went on sending under the old nick, which another user could then take. Now, whenever the relay passes on a NICK line and after the connection's own NICK is stored, the connection takes the nick its session holds in the database, read by session ID under the connection's lock. Taking the nick from the database rather than from the line means a connection can never follow another user's rename and send as them. Handlers read the nick under the same lock. Untested: an HTTP API rename landing while the connection's own NICK is being stored; that order cannot be produced reliably. Model: opus-5-5	2026-10-21 17:56:02 +02:00

Author

SHA1

Message

Date

sneak

d6a6296c1e

deploy (#189 )

check / check (push) Waiting to run

Details

Reviewed-on: #189

2026-10-22 18:52:00 +02:00

sneak

12a232ee1b

next → main: utility commands, IRC listener and audit fixes, build fixes (#111 )

check / check (push) Waiting to run

Details

Reviewed-on: #111

2026-10-22 18:27:05 +02:00

clawbot

d31fd529e2

Make an IRC listener connection follow its session's nick (closes #184 )

check / check (push) Canceled after 0s

Details

An IRC listener connection kept its own copy of its nick, so after the session's nick was changed from another client it went on sending under the old nick, which another user could then take. Now, whenever the relay passes on a NICK line and after the connection's own NICK is stored, the connection takes the nick its session holds in the database, read by session ID under the connection's lock. Taking the nick from the database rather than from the line means a connection can never follow another user's rename and send as them. Handlers read the nick under the same lock.

Untested: an HTTP API rename landing while the connection's own NICK is being stored; that order cannot be produced reliably.

Model: opus-5-5

2026-10-21 17:56:02 +02:00

Compare commits

Diff Content Not Available