One information about it: I guess it will be only obfuscated, so you can always decrypt the value if you know the source of GitLab. So I can't understand the problem with security, if there is an own dedicated machine and the gitlab.yml file is only readable for the root user (disable sudo or restrict it that the file can't be open) and so only the administrator can get the value/password. Finally he can get these values always. So there is no "real" security risk.
Am Donnerstag, 12. Juni 2014 21:13:47 UTC+2 schrieb Marcel Steves: > > That isn't possible at the moment, but afaik it should be changed in the > future. > > Am Donnerstag, 12. Juni 2014 16:07:35 UTC+2 schrieb kevin chaves: >> >> We want to encrypt the password in the configuration files when setting >> up the ldap server. Sorry if this wasn't clear, i don't know anything about >> servers. >> >> >> https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L118 >> >> ldap: enabled: false host: '_your_ldap_server' port: 636 uid: >> 'sAMAccountName' method: 'ssl' # "tls" or "ssl" or "plain" bind_dn: >> '_the_full_dn_of_the_user_you_will_bind_with' password: >> '_the_password_of_the_bind_user' >> >> >> -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/84ef004f-4226-4ee9-9ed7-6cbf24a9d591%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
