Richardbiely – User talk
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) No edit summary |
|||
| Line 12: | Line 12: | ||
::Adding origin ID is already considered and will very likely be implemented in the near future for security purposes. However, I'm currently not sure if we want it exposed to clients this way. [[User:Richardbiely|Richardbiely]] ([[User talk:Richardbiely|talk]]) 6:41, 28 May 2015 (CEST) | ::Adding origin ID is already considered and will very likely be implemented in the near future for security purposes. However, I'm currently not sure if we want it exposed to clients this way. [[User:Richardbiely|Richardbiely]] ([[User talk:Richardbiely|talk]]) 6:41, 28 May 2015 (CEST) | ||
:::The clents have no business knowing this, this is why it would be nice if this is available on server only as suggested above :) [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 07:58, 28 May 2015 (CEST) | |||
Revision as of 06:58, 28 May 2015
remoteExec
Dear Richard,
Would it be possible to somehow add a feature to remoteExecXXX command that would report the owner of the call origin? So the server can find out who used remoteExec and with what params.
Regards,
Killzone Kid (talk) 18:56, 27 May 2015 (CEST)
- I agree with this. Perhaps this could be achieved in the form of a new event handler. Passed arguments could be origin client ID, UID, Player profile name, remote execution target/s and executed command/function and arguments. This would really help sever admins keep track of network activity for security purposes. Benargee (talk) 19:51, 27 May 2015 (CEST)
- Adding origin ID is already considered and will very likely be implemented in the near future for security purposes. However, I'm currently not sure if we want it exposed to clients this way. Richardbiely (talk) 6:41, 28 May 2015 (CEST)
- The clents have no business knowing this, this is why it would be nice if this is available on server only as suggested above :) Killzone Kid (talk) 07:58, 28 May 2015 (CEST)