daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update default-settings.md

pull/2314/head
Luke Latham 2016-12-03 12:38:04 -06:00 committed by GitHub
parent becbdf4ca3
commit d9dd9d589c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/security/data-protection/configuration/default-settings.md
View File

@ -28,7 +28,7 @@ The system tries to detect its operational environment and provide good zero-con
4. If none of these conditions matches, keys are not persisted outside of the current process. When the process shuts down, all generated keys will be lost.
The developer is always in full control and can override how and where keys are stored. The first three options above should good defaults for most applications similar to how the ASP.NET <machineKey> auto-generation routines worked in the past. The final, fall back option is the only scenario that truly requires the developer to specify [configuration](overview.md) upfront if he wants key persistence, but this fall-back would only occur in rare situations.
The developer is always in full control and can override how and where keys are stored. The first three options above should good defaults for most applications similar to how the ASP.NET <machineKey> auto-generation routines worked in the past. The final, fall back option is the only scenario that truly requires the developer to specify [configuration](overview.md) upfront if they want key persistence, but this fall-back would only occur in rare situations.
>[!WARNING]
> If the developer overrides this heuristic and points the data protection system at a specific key repository, automatic encryption of keys at rest will be disabled. At rest protection can be re-enabled via [configuration](overview.md).