[olug] restricting ports on SSH forwarding

[Lou Duchez]

Thanks for the pointer; alas it's specific to OpenSSH.  Perhaps I need 
to install Win32-OpenSSH, which will hopefully include the 
authorized_keys functionality.

I went with freeSSHd because it installed easily and smoothly, and 
seemed to work well for the most part.  That's when it dawned on me that 
port forwarding comes with a BIG security risk ...


On 5/28/2020 8:22 PM, Reiners Cloud Consulting LLC wrote:
> I realize it's windows based ssh but maybe it has some similar flags to get
> you in pointed in the right direction.
>
> On Thu, May 28, 2020, 7:19 PM Justin Reiners <justin at hotlinesinc.com> wrote:
>
>> Here's a good write-up on restricting access, hope it helps
>>
>>
>> https://blog.tinned-software.net/restrict-ssh-access-to-port-forwarding-to-one-specific-port/
>>
>> On Thu, May 28, 2020, 6:41 PM Lou Duchez <lou at paprikash.com> wrote:
>>
>>> So SSH forwarding is a dandy way to get data to travel back and forth
>>> over a secure encrypted connection.  The only problem I'm aware of is,
>>> if I open up SSH port forwarding on my server to allow access to port
>>> 11111, there's nothing stopping a user from using the same SSH
>>> connection get at port 22222.
>>>
>>> ... or is there?  Any thoughts on how to limit the port forwarding on an
>>> SSH connection?  In particular I'm using freeSSHd on a Windows server,
>>> so if anyone knows anything about that, that would help.
>>> _______________________________________________
>>> OLUG mailing list
>>> OLUG at olug.org
>>> https://www.olug.org/mailman/listinfo/olug
>>>
>> _______________________________________________
>> OLUG mailing list
>> OLUG at olug.org
>> https://www.olug.org/mailman/listinfo/olug
>>
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://www.olug.org/mailman/listinfo/olug