View Issue Details

IDProjectCategoryView StatusLast Update
0005111unrealircdpublic2018-09-07 10:55
ReporterThe_MythAssigned Tosyzop 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
PlatformUnixOSUbuntuOS Version18.04 LTS
Product Version4.0.18 
Target Version4.2.0Fixed in Version4.2.0 
Summary0005111: SVSMODE -t does not remove vhost
DescriptionUsing /svsmode nick -t or /os umode nick -t to restore the predefined cloak of a user and with modes-on-connect "+ixw" and restrict-usermodes "x", the vHost of the user isn't actually removed.

I suppose that when we use the commands above described, it should act like if the user has done /hs off thus restoring the predefined cloak (in my case in the format XXX.ZZZ.YYY.IP).

This bug has been found by Le_Coyote and reported in #unreal-support and i can confirm it.

Hope the description is understandable. :D
Steps To Reproduce1) Set the vHost of a user with /hs set vHost
2) Use /svsmode nick -t or /os umode nick -t to unset the vHost of the user and restore the predefined cloak mask
3) /WHOIS the user and notice that the HostServ vHost is still active
TagsUMODE, VHOST
3rd party modulesNone that actually interfere with the above commands

Activities

syzop

2018-07-14 16:39

administrator   ~0020199

acknowledged and target for 4.0.19.

syzop

2018-09-07 10:55

administrator   ~0020283

Fixed, thanks for the report, as always :)

https://github.com/unrealircd/unrealircd/commit/858aaa774a409b65ee0e3ddefddbb7e63b86bf1d

Issue History

Date Modified Username Field Change
2018-07-04 13:47 The_Myth New Issue
2018-07-04 13:47 The_Myth Tag Attached: UMODE
2018-07-04 13:47 The_Myth Tag Attached: VHOST
2018-07-14 16:39 syzop Assigned To => syzop
2018-07-14 16:39 syzop Status new => acknowledged
2018-07-14 16:39 syzop Note Added: 0020199
2018-07-14 16:40 syzop Target Version => 4.2.0
2018-07-14 16:40 syzop Summary Removing vHost from users using /svsmode nick -t or /os umode nick -t, doesn't actually remove the vHost => SVSMODE -t does not remove vhost
2018-07-14 16:40 syzop Sticky Issue No => Yes
2018-09-07 10:55 syzop Status acknowledged => resolved
2018-09-07 10:55 syzop Resolution open => fixed
2018-09-07 10:55 syzop Fixed in Version => 4.2.0
2018-09-07 10:55 syzop Note Added: 0020283