Displaying 20 results from an estimated 7000 matches similar to: "[Bug 1857] New: [RFE] restrict port forwarding to localhost"
2008 Aug 27
18
[Bug 1513] New: CIDR address/masklen matching support for permitopen=
https://bugzilla.mindrot.org/show_bug.cgi?id=1513
           Summary: CIDR address/masklen matching support for permitopen=
           Product: Portable OpenSSH
           Version: 5.1p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: sshd
        AssignedTo: unassigned-bugs at mindrot.org
       
2016 Aug 02
0
[Bug 1857] [RFE] restrict port forwarding to localhost
https://bugzilla.mindrot.org/show_bug.cgi?id=1857
Damien Miller <djm at mindrot.org> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
--- Comment #6 from Damien Miller <djm at mindrot.org> ---
Close all resolved bugs after 7.3p1 release
2009 Jun 12
2
Restrict port forwarding on server
Hi,
Is there a way to restrict port forwarding on the server?
I want only port 8080 on the server to be available to clients.
Example when i give this command clients should be able to connect:
ssh -L 30300:localhost:8080 ....
When i give this for example clients should not be able to connect:
ssh -L 30300:localhost:4040 ....
I tried this option in config file of server:
PermitOpen
2002 Aug 13
1
[PATCH] global port forwarding restriction
Here's another patch for people providing ssh access to restricted
environments.
We allow our users to use port forwarding when logging into our mail
servers so that they can use it to fetch mail over an encrypted channel
using clients that don't support TLS, for example fetchmail.  (In fact,
fetchmail has built-in ssh support.) However we don't want them connecting
to other places
2018 Mar 26
23
[Bug 2846] New: PermitOpen rule in sshd_config is not case insensitive
https://bugzilla.mindrot.org/show_bug.cgi?id=2846
            Bug ID: 2846
           Summary: PermitOpen rule in sshd_config is not case insensitive
           Product: Portable OpenSSH
           Version: 7.6p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs
2010 Jul 18
20
[Bug 1800] New: PermitUserEnvironment accepting pattern of allowed userenv variables
https://bugzilla.mindrot.org/show_bug.cgi?id=1800
           Summary: PermitUserEnvironment accepting pattern of allowed
                    userenv variables
           Product: Portable OpenSSH
           Version: 5.5p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: sshd
        AssignedTo:
2006 Dec 05
3
[Bug 1267] PermitOpen - Multiple forwards don't works
http://bugzilla.mindrot.org/show_bug.cgi?id=1267
           Summary: PermitOpen - Multiple forwards don't works
           Product: Portable OpenSSH
           Version: v4.5p1
          Platform: ix86
        OS/Version: Cygwin on NT/2k
            Status: NEW
          Severity: security
          Priority: P2
         Component: sshd
        AssignedTo: bitbucket at mindrot.org
       
2007 Dec 12
58
[Bug 1402] New: [RFE] Support auditing through Linux Audit subsystem
https://bugzilla.mindrot.org/show_bug.cgi?id=1402
           Summary: [RFE] Support auditing through Linux Audit subsystem
    Classification: Unclassified
           Product: Portable OpenSSH
           Version: 4.7p1
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Keywords: patch
          Severity: normal
          Priority: P2
         Component: sshd
   
2009 Aug 12
2
Restrict a client port-forward to 1 port
Hi,
Is it possible to restrict a client port-forwarding to one port?
For example i want client X to open only port 1037 on server through
port-forwarding, client Y only port 1038 and so on...
How can this be possible?
I use private/public keys authentication.
Client version is openssh3.8p1, is windows client, and server version
is latest openssh on a linux machine.
Can anyone help please?
Thank
2020 May 05
1
[Bug 3159] New: authorized_keys: gap in port forwarding restrictions
https://bugzilla.mindrot.org/show_bug.cgi?id=3159
            Bug ID: 3159
           Summary: authorized_keys: gap in port forwarding restrictions
           Product: Portable OpenSSH
           Version: 8.0p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: sshd
          Assignee: unassigned-bugs
2011 Nov 06
13
[Bug 1949] New: PermitOpen none option
https://bugzilla.mindrot.org/show_bug.cgi?id=1949
             Bug #: 1949
           Summary: PermitOpen none option
    Classification: Unclassified
           Product: Portable OpenSSH
           Version: 5.9p1
          Platform: All
        OS/Version: OpenBSD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: sshd
        AssignedTo:
2010 Nov 04
8
[Bug 1833] New: incorrect completion of quoted directory
https://bugzilla.mindrot.org/show_bug.cgi?id=1833
           Summary: incorrect completion of quoted directory
           Product: Portable OpenSSH
           Version: 5.6p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: sftp
        AssignedTo: unassigned-bugs at mindrot.org
        ReportedBy: djm at
2017 May 05
3
[Bug 2711] New: Patch to add permitgwport and restrict permitopen to be a default deny
https://bugzilla.mindrot.org/show_bug.cgi?id=2711
            Bug ID: 2711
           Summary: Patch to add permitgwport and restrict permitopen to
                    be a default deny
           Product: Portable OpenSSH
           Version: 7.2p2
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component:
2023 Nov 12
1
Match Principal enhancement
AFAIK everything you described here could be done using the
AuthorizedKeysCommand or AuthorizedPrincipalsCommand directives. These
can emit authorized_keys options (inc. permitopen) as well as the allowed
keys/principals.
On Sun, 12 Nov 2023, Bret Giddings wrote:
> Hi OpenSSH devs,
> 
> I?m wondering if the following has any merit and can be done securely ...
> 
> If you could
2011 Feb 24
7
[Bug 1870] New: Do not show VisualHostKey unless attached to a terminal
https://bugzilla.mindrot.org/show_bug.cgi?id=1870
           Summary: Do not show VisualHostKey unless attached to a
                    terminal
           Product: Portable OpenSSH
           Version: 5.5p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: unassigned-bugs at
2008 Dec 02
12
[Bug 1542] New: Send echo on/off flag to SSH_ASKPASS
https://bugzilla.mindrot.org/show_bug.cgi?id=1542
           Summary: Send echo on/off flag to SSH_ASKPASS
           Product: Portable OpenSSH
           Version: -current
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: unassigned-bugs at mindrot.org
        ReportedBy: t8m at
2023 Nov 12
1
Match Principal enhancement
Hi OpenSSH devs,
I?m wondering if the following has any merit and can be done securely ...
If you could match on principals in the sshd_config, then (for example) on a gateway machine, you could have something like
/etc/ssh/authorized_keys/sshfwd:
cert-authority,principals=?batcha-fwd,batchb-fwd? ...
/etc/ssh/sshd_config containing:
Match User sshfwd
    PubkeyAuthentication            yes
 
2008 Aug 22
1
CIDR address/masklen matching support for permitopen="host:port" restrictions?
Dear openssh-unix-dev list,
in OpenSSH 5.1 you introduced CIDR address/masklen matching for "Match address" blocks in sshd_config as well as supporting CIDR matching in ~/.ssh/authorized_keys from="..." restrictions in sshd.
I wonder whether CIDR address/masklen matching will be implemented for permitopen="host:port" restrictions in sshd as well, that would be quite
2010 Jul 15
13
[Bug 1798] New: Add fsync() support to sftp/sftp-server
https://bugzilla.mindrot.org/show_bug.cgi?id=1798
           Summary: Add fsync() support to sftp/sftp-server
           Product: Portable OpenSSH
           Version: -current
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: sftp-server
        AssignedTo: unassigned-bugs at mindrot.org
       
2009 Jan 30
12
[Bug 1552] New: Patch to log tunnel information
https://bugzilla.mindrot.org/show_bug.cgi?id=1552
           Summary: Patch to log tunnel information
           Product: Portable OpenSSH
           Version: 5.1p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: sshd
        AssignedTo: unassigned-bugs at mindrot.org
        ReportedBy: jblaine at