Revert of Forward password-store switch to OSCrypt component

Revert of Forward password-store switch to OSCrypt component (patchset #15 id:310001 of https://codereview.chromium.org/2118443002/ )

Reason for revert:
mahmadi@ reported reaching the DCHECK in components/os_crypt/os_crypt_linux.cc

Original issue's description:
> Forward password-store switch to OSCrypt component
>
> Password manager uses a switch to allow the user to override the
> auto-detection of the appropriate password store. OSCrypt should
> respect this switch as well.
>
> The switch value is read and passed to OSCrypt at a very early
> point in Chrome's start, before any of OSCrypt's dependents
> use it.
>
> I also reworked OSCrypt's build to make it simpler for chrome to
> deduce whether the linux implementation of OSCrypt will be used.
>  - Previously, os_crypt_linux was used only if we also decided to
>    link at least one linux backend. Otherwise we used os_crypt_posix.
>  + Now, we always use the linux implementation for linux. If no
>    KeyStorage is linked, the linux implementation defaults to the
>    same behavior as for posix.
>
> BUG=602624
>
> Committed: https://crrev.com/92699e345c15243c4023a8739101333ed2658e37
> Cr-Commit-Position: refs/heads/master@{#405114}

TBR=thestig@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602624
Committed: https://crrev.com/7e8f3ac9fc9e4a8588e900b7fce5492c26da1986
Cr-Commit-Position: refs/heads/master@{#405197}

[cfroussios, 2016-07-13 16:53:49]

The CQ bit was checked by cfroussios@chromium.org

[cfroussios, 2016-07-13 16:53:49]

Created Revert of Forward password-store switch to OSCrypt component

[commit-bot: I haz the power, 2016-07-13 16:54:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-13 16:54:23]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-13 16:54:23]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[engedy, 2016-07-13 16:56:42]

Rubberstamp LGTM.

[cfroussios, 2016-07-13 16:57:16]

The CQ bit was checked by cfroussios@chromium.org

[commit-bot: I haz the power, 2016-07-13 16:57:41]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-13 16:58:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-13 16:59:57]

Description was changed from

==========
Revert of Forward password-store switch to OSCrypt component (patchset #15
id:310001 of https://codereview.chromium.org/2118443002/ )

Reason for revert:
mahmadi@ reported reaching the DCHECK in components/os_crypt/os_crypt_linux.cc

Original issue's description:
> Forward password-store switch to OSCrypt component
> 
> Password manager uses a switch to allow the user to override the
> auto-detection of the appropriate password store. OSCrypt should
> respect this switch as well.
> 
> The switch value is read and passed to OSCrypt at a very early
> point in Chrome's start, before any of OSCrypt's dependents
> use it.
> 
> I also reworked OSCrypt's build to make it simpler for chrome to
> deduce whether the linux implementation of OSCrypt will be used.
>  - Previously, os_crypt_linux was used only if we also decided to
>    link at least one linux backend. Otherwise we used os_crypt_posix.
>  + Now, we always use the linux implementation for linux. If no
>    KeyStorage is linked, the linux implementation defaults to the
>    same behavior as for posix.
> 
> BUG=602624
> 
> Committed: https://crrev.com/92699e345c15243c4023a8739101333ed2658e37
> Cr-Commit-Position: refs/heads/master@{#405114}

TBR=thestig@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602624
==========

to

==========
Revert of Forward password-store switch to OSCrypt component (patchset #15
id:310001 of https://codereview.chromium.org/2118443002/ )

Reason for revert:
mahmadi@ reported reaching the DCHECK in components/os_crypt/os_crypt_linux.cc

Original issue's description:
> Forward password-store switch to OSCrypt component
>
> Password manager uses a switch to allow the user to override the
> auto-detection of the appropriate password store. OSCrypt should
> respect this switch as well.
>
> The switch value is read and passed to OSCrypt at a very early
> point in Chrome's start, before any of OSCrypt's dependents
> use it.
>
> I also reworked OSCrypt's build to make it simpler for chrome to
> deduce whether the linux implementation of OSCrypt will be used.
>  - Previously, os_crypt_linux was used only if we also decided to
>    link at least one linux backend. Otherwise we used os_crypt_posix.
>  + Now, we always use the linux implementation for linux. If no
>    KeyStorage is linked, the linux implementation defaults to the
>    same behavior as for posix.
>
> BUG=602624
>
> Committed: https://crrev.com/92699e345c15243c4023a8739101333ed2658e37
> Cr-Commit-Position: refs/heads/master@{#405114}

TBR=thestig@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602624

Committed: https://crrev.com/7e8f3ac9fc9e4a8588e900b7fce5492c26da1986
Cr-Commit-Position: refs/heads/master@{#405197}
==========

[commit-bot: I haz the power, 2016-07-13 16:59:58]

Patchset 1 (id:??) landed as
https://crrev.com/7e8f3ac9fc9e4a8588e900b7fce5492c26da1986
Cr-Commit-Position: refs/heads/master@{#405197}

[cfroussios, 2016-07-14 13:09:47]

Description was changed from

==========
Revert of Forward password-store switch to OSCrypt component (patchset #15
id:310001 of https://codereview.chromium.org/2118443002/ )

Reason for revert:
mahmadi@ reported reaching the DCHECK in components/os_crypt/os_crypt_linux.cc

Original issue's description:
> Forward password-store switch to OSCrypt component
>
> Password manager uses a switch to allow the user to override the
> auto-detection of the appropriate password store. OSCrypt should
> respect this switch as well.
>
> The switch value is read and passed to OSCrypt at a very early
> point in Chrome's start, before any of OSCrypt's dependents
> use it.
>
> I also reworked OSCrypt's build to make it simpler for chrome to
> deduce whether the linux implementation of OSCrypt will be used.
>  - Previously, os_crypt_linux was used only if we also decided to
>    link at least one linux backend. Otherwise we used os_crypt_posix.
>  + Now, we always use the linux implementation for linux. If no
>    KeyStorage is linked, the linux implementation defaults to the
>    same behavior as for posix.
>
> BUG=602624
>
> Committed: https://crrev.com/92699e345c15243c4023a8739101333ed2658e37
> Cr-Commit-Position: refs/heads/master@{#405114}

TBR=thestig@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602624

Committed: https://crrev.com/7e8f3ac9fc9e4a8588e900b7fce5492c26da1986
Cr-Commit-Position: refs/heads/master@{#405197}
==========

to

==========
Revert of Forward password-store switch to OSCrypt component (patchset #15
id:310001 of https://codereview.chromium.org/2118443002/ )

Reason for revert:
mahmadi@ reported reaching the DCHECK in components/os_crypt/os_crypt_linux.cc

Original issue's description:
> Forward password-store switch to OSCrypt component
>
> Password manager uses a switch to allow the user to override the
> auto-detection of the appropriate password store. OSCrypt should
> respect this switch as well.
>
> The switch value is read and passed to OSCrypt at a very early
> point in Chrome's start, before any of OSCrypt's dependents
> use it.
>
> I also reworked OSCrypt's build to make it simpler for chrome to
> deduce whether the linux implementation of OSCrypt will be used.
>  - Previously, os_crypt_linux was used only if we also decided to
>    link at least one linux backend. Otherwise we used os_crypt_posix.
>  + Now, we always use the linux implementation for linux. If no
>    KeyStorage is linked, the linux implementation defaults to the
>    same behavior as for posix.
>
> BUG=602624
>
> Committed: https://crrev.com/92699e345c15243c4023a8739101333ed2658e37
> Cr-Commit-Position: refs/heads/master@{#405114}

TBR=thestig@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=602624

Committed: https://crrev.com/7e8f3ac9fc9e4a8588e900b7fce5492c26da1986
Cr-Commit-Position: refs/heads/master@{#405197}
==========