-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add extensions/cap_realhost #13
Conversation
The ideal would be possible if the outbound_msgbuf hook included the target information. Otherwise, seems fine to me. |
As it stands the hook is called just once for something like a channel message, even though it goes out to lots of users, and the send machinery takes care of formatting different concrete lines for people with distinct capability sets. I'd like to keep that, so we probably need to teach the sending stuff about privs. |
68ebe7a
to
fc11487
Compare
fc11487
to
82f3a65
Compare
Sigyn approves |
If they can see it it's already in the message source
7480dfe
to
d611aeb
Compare
Implements the
solanum.chat/realhost
client capability, which sends thesolanum.chat/realhost
andsolanum.chat/ip
vendor tags on user-sourced messages as appropriate.Hidden IPs and hostnames are sent to
auspex:hostname
opers. For consistency, if a remote oper wouldn't see an IP (because it's behind an IP spoof and not propagated), it's not shown to local opers either. Internally the oper version of the tag is implemented with an invisible cap named?oper_realhost
.originally: I'm not terribly happy with the state of this, but improving it depends on having tags that are gated by privs, which may itself depend on changing how privsets work.
Ideally the cap would be available to all users, but just wouldn't reveal hidden information to the unprivileged.