Renames secure_hash_nss.cc to secure_hash.cc

Renames secure_hash_nss.cc to secure_hash.cc
(there's an exclusion for _nss on non-linux platforms, however we need
this file for mac and windows as well.)
this is a build fix for http://src.chromium.org/viewvc/chrome?view=rev&revision=72782)

BUG=none
TEST=compiles

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=72783

[bulach, 2011-01-27 11:44:18]

Hi Denis, Hans, would you please take a quick look?

I renamed the file so that it's included in non-linux platforms.

[glotov, 2011-01-27 11:47:29]

LGTM

On 2011/01/27 11:44:18, bulach wrote:
> Hi Denis, Hans, would you please take a quick look?
> 
> I renamed the file so that it's included in non-linux platforms.

[bulach, 2011-01-27 11:54:32]

thanks! landing it now..

[wtc, 2011-01-27 17:56:41]

LGTM.

Would you prefer secure_hash_builtin.cc or secure_hash_default.cc?

[bulach, 2011-01-27 18:01:59]

I can certainly do that. should I also rename sha2.cc?
I think "default" sounds better than "builtin" as it still requires a third
party library, what do you think?

On 2011/01/27 17:56:41, wtc wrote:
> LGTM.
> 
> Would you prefer secure_hash_builtin.cc or secure_hash_default.cc?

[wtc, 2011-01-27 18:12:48]

Using "_default" is fine.

Let's not rename sha2.cc because that file name comes from NSS (sha2.c,
originally a C file).