[DOCS-1325] TCP best practices for Windows Created: 02/Apr/13 Updated: 22/Apr/13 Resolved: 22/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 44 weeks, 5 days ago |
| Description |
|
A user just shared a link about tcp settings best practices for Windows deployments. Do you think it's worth mentioning in the docs (the article also indirectly contains the method to set the keepalive in Windows): http://technet.microsoft.com/en-us/library/dd349797.aspx |
| Comments |
| Comment by Andreas Nilsson [ 12/Apr/13 ] |
|
Agree w Ken. There is a bunch of security configurations relating to a Mongo deployment that we not necessarily want to involve ourselves with IMO. It could be things like IdM management of server administrator accounts, general hardening of servers OS etc. |
| Comment by Ken Thompson [ 02/Apr/13 ] |
|
This is how apps are run at Microsoft as its their best practice for tcp hardening. Reference it as an MS best practice in our docs accordingly. |