Sam, Scalr uses farm key to authenticate itself.
You can change encryption algorithm in /etc/login.defs file. Nick 2009/9/21 Sam <[email protected]>: > > I Will confirm that later, Nickolas. > > At the moment linux/unixes use CRYPT_MD5 or CRYPT_BLOWFISH. > Our old server use CRYPT_MD5 whereas the new also uses > CRYPT_BLOWFISH. > > If I change these settings will it affect any scalr functionality? > Do you know where can I change the salt value and the encryption > algorithm from CRYPT_BLOWFISH to CRYPT_MD5 in ubuntu app server > image? > > > On Sep 21, 12:30 pm, Nickolas Toursky <[email protected]> wrote: >> Sam, >> >> Do you mean system users passwords in /etc/shadow ? >> >> Nick >> >> 2009/9/21 Sam <[email protected]>: >> >> >> >> >> >> > We were using Red hat and then migrated to the cloud servers on >> > Ubuntu. >> >> > The current Red Hat implementation of the password encryption uses >> > the >> > crypt() method with a generated salt. On the Red Hat server the method >> > uses the md5 algorithm to generate >> > passwords and the constant values are: >> > CRYPT_SALT_LENGTH - 12 >> > CRYPT_STD_DES - 1 >> > CRYPT_EXT_DES - 0 >> > CRYPT_MD5 - 1 >> > CRYPT_BLOWFISH - 0 >> >> > For example, the generated password of the string 'admin' was >> > $1$BOqLtPNm$CnzfaoymJGNvotH7ZPoqB/ - all hash values begin $1$, then >> > 8 >> > characters, then a $ sign. >> >> > On the Ubuntu setup, it seems that the Standard DES algorithm is >> > always used. >> >> > Any ideas how to force the use of md5? In theory this is based on >> > the >> > length of the supplied salt, but it doesn't seem to work. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
