wire_expression2_concmd_whitelist (filters for concmd)

[Anticept]

wire_expression2_concmd 1
wire_expression2_concmd_whitelist ""
=> allow everything (=previous wire_expression2_concmd 1 behaviour)

Should make this sound more intimidating, like print out a warning when the white-list is cleared... or have to type in "Global_Allow", something like that.

The warning could be something along the lines of "Warning, E2 console whitelist behavior is off, E2 can now potentially be used as an exploit to gain complete access to clients and the server" and it will be sent to EVERYONE.

[feha]

Anticept, I thought it was supposed to be clientsided...

Also, you have to put all concmds in same line of a concmd? Would be much better if you made "" clear the whitelist, and everything else add to the whitelist.

And then perhaps the wire_expression2_concmd 2 as someone suggested, to just temporary turn off whitelist.


Also, you could have a concmd then to remove a concmd of your choice from the whitelist, liek a blacklist would work. (making whitelist "" and then the remove actaully work liek a blacklist).

[Zantier]

Yeah, isn't the only danger from writing self-destructive code, or duping someone else's?

[Anticept]

Anticept, I thought it was supposed to be clientsided...
.

Yeah I was told it was clientside, however it still might be useful to notify everyone in the server. Social engineering is evil.

[ColinSSX]

Yeah I was told it was clientside, however it still might be useful to notify everyone in the server. Social engineering is evil.

How about keeping it completely client side? To me alerting everyone would just be fucking annoying.

It's basically saying "TARGET THIS PERSON, HE HAS FILTERING OFF!"

[Mujibar]

*Agreed with above post.

This is really good, has it been put into the SVN?

[ColinSSX]

*Agreed with above post.

This is really good, has it been put into the SVN?

Yep, it's all done and ready for use!