Val Polyakov wrote, On 9/15/10 3:51 PM:
Plaintext.
But that doesnt matter - because its a RT db, with nothing else on it.
Security has no problem with it.
They only have a problem with storing the domain account credentials in
plaintext.
I'm not sure that it will satisfy the people you are tr
> > Solutions like "well make the file only readable by root" aren't going to
> > be accepted (not by me, but by our security team). Needs to be a hashed
> > password, may be, or something.. I don't know.. soliciting ideas.
> >
When people talk about hashes, they are _typically_ talking about
one-
Any thoughts, anyone ?
> Hello,
>
> what are our options as far as securing RT_SiteConfig.pm goes?
>
> My company has pretty strict security requirements, and our security team
> will simply not allow us to store the ldap username/password in a plain
> text file on the RT server (and I can fully u
Plaintext.
But that doesnt matter - because its a RT db, with nothing else on it.
Security has no problem with it.
They only have a problem with storing the domain account credentials in
plaintext.
--Val
> On 09/15/2010 12:52 PM, Val Polyakov wrote:
>> Hello,
>>
>> what are our options as far
On 09/15/2010 12:52 PM, Val Polyakov wrote:
Hello,
what are our options as far as securing RT_SiteConfig.pm goes?
My company has pretty strict security requirements, and our security team
will simply not allow us to store the ldap username/password in a plain
text file on the RT server (and I
Hello,
what are our options as far as securing RT_SiteConfig.pm goes?
My company has pretty strict security requirements, and our security team
will simply not allow us to store the ldap username/password in a plain
text file on the RT server (and I can fully understand their concerns).
What are
