What is a one sentence summary of your feature request?
Provide destination details for applications like PowerShell and WinSCP
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Provide destination details for PowerShell and WinSCP. We have instances where we permit use of intellectual property with applications like PowerShell and WinSCP, but would appreciate the ability to restrict based on destination details. (eg. using winscp or powershell to interface with trusted IP and share data, vs using it to send to untrusted locations.)
How do you currently solve the challenges you have by not having this feature?
We appreciate your patience while we technically reviewed your request.
At the moment, unfortunately we’re unable to decrypt WinSCP connections, which means we cannot capture these specific details. Should things evolve going forward, we’ll make sure to reconsider your improvement suggestion.
However, we are planning an improvement that will allow all Git operations over SSH connection (such as fetch, pull, and push) to be blocked when configured. This will help ensure consistent control across all Git SSH usage. This improvement is on its way and will be delivered in one of the upcoming EPP Client Releases.
If you have any other questions, let me know. Thank you for your understanding.