2017-10-12 07:05:46 +08:00
## WCF PipeConnection.GetHashAlgorithm now uses SHA256
2017-09-28 07:17:51 +08:00
2017-10-12 07:05:46 +08:00
### Scope
2017-09-28 07:17:51 +08:00
Minor
2017-10-12 07:05:46 +08:00
### Version Introduced
4.7.1
### Source Analyzer Status
2017-09-28 07:17:51 +08:00
NotPlanned
2017-10-12 07:05:46 +08:00
### Change Description
2017-10-04 03:20:10 +08:00
Starting with the .NET Framework 4.7.1, Windows Communication Foundation uses a SHA256 hash to generate random names for named pipes. In the .NET Framework 4.7 and earlier versions, it used a SHA1 hash.
2017-09-28 07:17:51 +08:00
2017-12-02 01:35:54 +08:00
- [ ] Quirked
- [ ] Build-time break
2017-10-24 01:08:47 +08:00
### Recommended Action
2017-10-04 03:20:10 +08:00
If you run into compatibility issue with this change on the .NET Framework 4.7.1 or later, you can opt-out it by adding the following line to the `<runtime>` section of your app.config file:
2017-09-28 07:17:51 +08:00
2017-10-04 03:20:10 +08:00
```xml
< configuration >
< runtime >
< AppContextSwitchOverrides value = "Switch.System.ServiceModel.UseSha1InPipeConnectionGetHashAlgorithm=true" / >
2017-10-24 01:08:47 +08:00
< / runtime >
2017-10-04 03:20:10 +08:00
< / configuration >
```
2017-10-24 01:08:47 +08:00
2017-10-24 01:46:29 +08:00
### Affected APIs
2017-09-28 07:17:51 +08:00
* Not detectable via API analysis
2017-10-04 03:20:10 +08:00
### Category
2017-10-26 03:51:47 +08:00
Windows Communication Foundation (WCF)
2017-10-04 03:20:10 +08:00
2017-09-28 07:17:51 +08:00
<!--
### Original Bug
[395685] (https://devdiv.visualstudio.com/web/wi.aspx?pcguid=011b8bdf-6d56-4f87-be0d-0092136884d9& id=395685)
2017-10-04 03:20:10 +08:00
-->
2017-09-28 07:17:51 +08:00
