Fail closed for SMB referral transports
This commit is contained in:
@@ -60,9 +60,10 @@ Every provider must:
|
||||
- use a transport that pins every connection to a policy-validated DNS/IP answer
|
||||
and revalidates redirects; SDK transports without that guarantee fail closed
|
||||
|
||||
SMB DNS endpoints therefore fail closed in private-network mode until the SDK
|
||||
supports connection-time pinning; explicit IP endpoints remain available. Live
|
||||
S3 access is disabled in all modes until `boto3`/botocore can be bound to the
|
||||
Live SMB access is disabled in all modes until `smbprotocol` initial connections
|
||||
and DFS referral targets can be pinned and policy-validated. An explicit IP is
|
||||
not sufficient because the server may still issue a referral to another peer.
|
||||
Live S3 access is likewise disabled until `boto3`/botocore can be bound to the
|
||||
pinned transport, including SDK-managed redirects and endpoint discovery.
|
||||
|
||||
## Non-Goals For Files
|
||||
|
||||
Reference in New Issue
Block a user