[
https://issues.apache.org/jira/browse/MESOS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032862#comment-14032862
]
Niklas Quarfot Nielsen commented on MESOS-1486:
-----------------------------------------------
I have no problem turning this ticket into a sub ticket under something like
"Add mechanisms to prevent rogue masters" and the log replicas sound like a
serious problem in that case too.
But even with that fixed, a single rogue master could fake registration with a
slave, no?
> Add whitelisting of masters in slaves.
> --------------------------------------
>
> Key: MESOS-1486
> URL: https://issues.apache.org/jira/browse/MESOS-1486
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Niklas Quarfot Nielsen
> Assignee: Niklas Quarfot Nielsen
>
> Like masters can whitelist slaves (and only announce available resources from
> slaves whitelisted), slaves should be able to whitelist masters they are
> willing/allowed to connect to. I have a proof-of-concept ready which ties
> into the slave::detected() method and prevents non-whitelisted masters to
> register.
> If "*" is provided - whitelisting is not enforced (which would be the usual
> case).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
