Hi, This configuration is applied on Scalarizr startup, so upgrade or just service restart will override your settings.
What cloud platform are you running? This setting is required only by OpenStack/CloudStack but currently applied everywhere, and we'll tweak this in nearest update. Regards, Marat On Monday, August 24, 2015 at 11:24:50 PM UTC+3, Dmitri Toubelis wrote: > > Hi, > > I was battling a problem that only occurs with instances instantiated by > Scalr and finally i figured it out. I noticed that Scalarizr agent add the > following lines to `/etc/ssh/sshd_config file`: > > ... > PubkeyAuthentication yes > RSAAuthentication yes > *AuthorizedKeysFile %h/.ssh/authorized_keys* > > The last line is what causes the problem. The default value for > `AuthorizedKeysFile ` is “.ssh/authorized_keys .ssh/authorized_keys2” > according to sshd documentation so the new value disables > ".ssh/authorized_keys2" part and it causes problems with some apps (freenx > in particular). > > I can obviously overwrite configuration by a script to fix this problem > but I wonder if Scalarizr require this particular configuration for some > reasons. Also, I have a suspicion that Scalarizr may restore this > configuration on upgrade, I will not be able to capture this event and it > will break the system. > > So, my question is what would be the best way to address this issue? > > Thanks. > > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
