[DOCS-12793] [Server] Specify that GCM is supported when used as a stream cipher for transport encryption on Windows Created: 11/Jun/19  Updated: 30/Oct/23  Resolved: 21/Aug/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Critical - P2
Reporter: Luke Prochazka Assignee: Nick Villahermosa
Resolution: Fixed Votes: 0
Labels: reopened, server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All platforms, but specifically Windows


Issue Links:
Related
Participants:
Days since reply: 24 weeks, 2 days ago

 Description   

Description

The cited docs links below make reference to the GCM cipher being unsupported on Windows:

https://docs.mongodb.com/manual/release-notes/4.0/index.html#aes-gcm
https://docs.mongodb.com/manual/release-notes/4.0-compatibility/index.html#aes-gcm
https://docs.mongodb.com/manual/tutorial/configure-encryption/index.html#overview

However we need to clarify that this limitation applies only in the context of using GCM as a block cipher with the At-Rest-Encryption feature on Windows. This limitation does not apply to GCM being used as a stream cipher for transport encryption on Windows (via schannel).

The current documentation invites ambiguity to this effect, and this DOCS request is to clarify the scope and limitation with respect to the GCM cipher.

Scope of changes

  • Update specified pages to note limited scope of restriction

    Impact to Other Docs

    MVP (Work and Date)

    Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Nick Villahermosa [ 21/Aug/23 ]

Backports: v6.0, v5.0, v4.4

Comment by Ashley Brown [ 31/May/23 ]

Bumping priority due to linked HELP ticket. 

Generated at Thu Feb 08 08:06:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.