4

I have to be missing something here.

It just hit me as added a new node to my cluster in order to prepare for the removal of a different node: "How does the cluster know that it is okay to send the new node a SST?"

I am pretty sure that the only information the new node has about the cluster is the gcomm:// address. Surely that isn't looked at as "secure" information that passes for authentication. To my knowledge, no shell account on the new node has the same password as on the existing cluster nodes.

So what would prevent anyone from spinning up a new node and pointing it's gcomm:// address at one or more of my nodes to just get an SST and be able to see all of my data?

Of course, certificates will be put in place. But I'm talking about a default setup and how things work "out of the box." I couldn't find much of anything that talked about this out there.

Am I going nuts?

  • Looking through /usr/bin/wsrep_sst_rsync, I see: rsync --owner --group --perms --links --specials --ignore-times --inplace --dirs --delete --quiet $WHOLE_FILE_OPT -f '+ /ib_logfile[0-9]*' -f '- **' "$WSREP_LOG_DIR/" rsync://$WSREP_SST_OPT_ADDR-log_dir Trying to manually run rsync on the command line in a similar fashion fails, but I may not be recreating the exact command line properly. – Shaun McPeck Oct 7 '15 at 17:17
  • Also - might this be better suited for serverfault? What do people think? – Shaun McPeck Oct 7 '15 at 17:20
0

The cluster simply doesn't know. It'll send a sst to every node which requests it.

  • 2
    Can you provide a reference/source to back this up? – Shaun McPeck Oct 7 '15 at 16:19
  • @ShaunMcPeck you observed this in your own experiment, no? – eckes Aug 14 at 7:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.