You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UserAgent is currently hardcoded in Go SDK
which why it is possible to use policy like this to allow access to buckets with S3 but prevent it from SFTP clients:
Describe the solution you'd like
It would be nice if SFTP server would have own documented UserAgent which can be used to block SFTP connections.
Also would be nice if SourceIp would works same way that for S3 connections. It should be possible to to achieve it by setting SFTP client IP to header X-Forwarded-For when calling backend.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Values would be something like MinIO SFTP Server in user agent and ssh.ConnMetadata.RemoteAddr() (which should contain client IP) in X-Forwarded-For header.
Context is ability to have MinIO's SFTP server published to internet but block those connections from everyone else than whitelisted sources.
Is your feature request related to a problem? Please describe.
SourceIp
SFTP server connects to MinIO by using localhost address
minio/cmd/sftp-server-driver.go
Line 83 in 8b660e1
which why it is possible to use policy like this to allow access to buckets with S3 but prevent it from SFTP clients:
UserAgent
UserAgent is currently hardcoded in Go SDK
which why it is possible to use policy like this to allow access to buckets with S3 but prevent it from SFTP clients:
Describe the solution you'd like
It would be nice if SFTP server would have own documented UserAgent which can be used to block SFTP connections.
Also would be nice if
SourceIp
would works same way that for S3 connections. It should be possible to to achieve it by setting SFTP client IP to headerX-Forwarded-For
when calling backend.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: