coming to it ?
> >
> > > From: jain.garim...@gmail.com
> > > Date: Mon, 27 Jun 2016 16:02:37 +0530
> > > Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> > > To: dev@mina.apache.org
> > >
> > > Hey,
> > >
> > &
ich I wrote in Java but never
> published it). If you want to setup SSHD on non-standard port, then why do
> you need to reject SSHD connections coming to it ?
>
> > From: jain.garim...@gmail.com
> > Date: Mon, 27 Jun 2016 16:02:37 +0530
> > Subject: Re: Partial Disab
mail.com
> Date: Mon, 27 Jun 2016 16:02:37 +0530
> Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> To: dev@mina.apache.org
>
> Hey,
>
> Is there a way I can override the method doAuth under
> UserAuthPublicKey.java to return back if the connection s
016 00:04:31 +0530
> > Subject: RE: Partial Disabling of port 22 using apache-mina SSHD
> > From: jain.garim...@gmail.com
> > To: dev@mina.apache.org
> >
> > Hey, thanks for the detailed info. Is there any way we can have a chat
> > other than mail communication in
Sorry, mail communication is best I can do for now...
> Date: Wed, 22 Jun 2016 00:04:31 +0530
> Subject: RE: Partial Disabling of port 22 using apache-mina SSHD
> From: jain.garim...@gmail.com
> To: dev@mina.apache.org
>
> Hey, thanks for the detailed info. Is there any way
good chances you will find a
> suitable example similar to what you want to achieve.
> The same applies for the server side, although it is a bit tricker...Hope
> this gives you a good lead how to proceed.
>
> > Date: Tue, 21 Jun 2016 22:45:57 +0530
> > Subject: R
re
very good chances you will find a suitable example similar to what you want to
achieve.
The same applies for the server side, although it is a bit tricker...Hope this
gives you a good lead how to proceed.
> Date: Tue, 21 Jun 2016 22:45:57 +0530
> Subject: RE: Partial Disabling of port 2
(and any
> other channel - e.g. PROXY, SOCKS, etc...)..
>
> > From: jain.garim...@gmail.com
> > Date: Tue, 21 Jun 2016 11:42:58 +0530
> > Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> > To: dev@mina.apache.org
> >
> > Can I keep the port op
session. The port
is always 22 (SSH) for SFTP and SCP (and any other channel - e.g. PROXY, SOCKS,
etc...)..
> From: jain.garim...@gmail.com
> Date: Tue, 21 Jun 2016 11:42:58 +0530
> Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> To: dev@mina.apache.org
>
> C
t; and
>>> >> bind SFTP to the public interface on port 22 - easy to do just call
>>> >> "setAddress" (or something to that effect) on the SshServer instance
>>> >> I could think of more exotic options - e.g. similar to sslh, using
>>> &
face (e.g., 127.0.0.1)om port 22
>> and
>> >> bind SFTP to the public interface on port 22 - easy to do just call
>> >> "setAddress" (or something to that effect) on the SshServer instance
>> >> I could think of more exotic options - e.g. simil
ce
> >> I could think of more exotic options - e.g. similar to sslh, using
> >> HAPROXY, etc., etc.
> >> > From: jain.garim...@gmail.com
> >> > Date: Mon, 20 Jun 2016 12:10:26 +0530
> >> > Subject: Re: Partial Disabling of port 22 using apache-mina
t 22 - easy to do just call
>> "setAddress" (or something to that effect) on the SshServer instance
>> I could think of more exotic options - e.g. similar to sslh, using
>> HAPROXY, etc., etc.
>> > From: jain.garim...@gmail.com
>> > Date: Mon
think of more exotic options - e.g. similar to sslh, using
> HAPROXY, etc., etc.
> > From: jain.garim...@gmail.com
> > Date: Mon, 20 Jun 2016 12:10:26 +0530
> > Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> > To: dev@mina.apache.org
> >
> >
:10:26 +0530
> Subject: Re: Partial Disabling of port 22 using apache-mina SSHD
> To: dev@mina.apache.org
>
> Hi elijah,
>
> The requirement is to block port 22 for SSH and accept SFTP connections on
> Port 22. Is there a class/method that can help us achieve the aim?
>
&g
Hi elijah,
The requirement is to block port 22 for SSH and accept SFTP connections on
Port 22. Is there a class/method that can help us achieve the aim?
-Garima Jain.
On Fri, Jun 17, 2016 at 3:27 PM, elijah baley wrote:
> Is there some reason your code cannot examine the incoming client addres
Hi,
The code is accepting the traffic coming on port 9822 and forwarding it to
22. But while connecting over ssh on port 22, the server is accepting a
connection.
Is there a way from the library itself to handle the condition.
-Garima Jain.
On Fri, Jun 17, 2016 at 3:27 PM, elijah baley wrote:
Is there some reason your code cannot examine the incoming client address and
reject it if it does not match some specified criteria (e.g., mask, network,
closed group of IPs - whatever...) ?
> From: jain.garim...@gmail.com
> Date: Fri, 17 Jun 2016 14:50:51 +0530
> Subject: Partial Disabling of
18 matches
Mail list logo