Agreed, there is no need for RAET even as tech preview if we know it does not have a bright future either. However the main issue should also be handled, as raet itself was not the cause of the crash but the way it is packaged/shipped: There are config files shipped in packages for the minion that have -rw-r--r-- root:root that may be read from the master. Most of master config is: drwxr-x--- root:salt package salt-raet shipped config files for both in a single package, and master reads minion config, ergo permission denied. Is there a reason for not having everything as drwxr-x--- root:salt on both sides? private keys?.