You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2017/02/10 17:51:41 UTC

[jira] [Commented] (MESOS-7086) Tighten up rules on IDs used in Mesos

    [ https://issues.apache.org/jira/browse/MESOS-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861592#comment-15861592 ] 

Yan Xu commented on MESOS-7086:
-------------------------------

Some precursors: 
https://reviews.apache.org/r/56526/
https://reviews.apache.org/r/56527/

> Tighten up rules on IDs used in Mesos
> -------------------------------------
>
>                 Key: MESOS-7086
>                 URL: https://issues.apache.org/jira/browse/MESOS-7086
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Yan Xu
>            Assignee: Yan Xu
>
> We currently have pretty relaxed rules on validity of IDs (e.g., TaskID, ExecutorID, PersistenceID):
> https://github.com/apache/mesos/blob/7a3df44eb6a59bd95604fd38a18dc745363d468d/src/common/validation.cpp
> https://github.com/apache/mesos/blob/7a3df44eb6a59bd95604fd38a18dc745363d468d/src/slave/validation.cpp#L40
> We should tighten up the restrictions to prevent misleading and exploitable ID and document these rules.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)