On Sat, Jan 12, 2008 at 07:04:08PM +, Sean Miller wrote:
> He wanted a sshd listening on port 22 for his tomboy or whatever, yet didn't
> want it exposed to the internet.
>
Actually he only wanted port 22 used becasue he could not figure out how to
tell tomboy what port to use. Now Chris and
Sean Miller wrote:
> I run all my sshd servers (on the www) on 23432.
>
> Easy to remember but not the first place the hackers look.
Hello, Sean.
They will now ;-)
> So I think it's definitely worth doing... but if you're on a home
> network and have a router and need port 22 for your local ac
On 1/12/08, Chris Smith <[EMAIL PROTECTED]> wrote:
>
> I run my own SSH servers on the same ports internally and externally
> means I only need one ~/.ssh/config which keeps everything much more sane.
Yes, but that wasn't the question.
He wanted a sshd listening on port 22 for his tomboy or what
Sean Miller wrote:
> I run all my sshd servers (on the www) on 23432.
>
> Easy to remember but not the first place the hackers look.
>
> So I think it's definitely worth doing... but if you're on a home network
> and have a router and need port 22 for your local access why not use the
> router to
I run all my sshd servers (on the www) on 23432.
Easy to remember but not the first place the hackers look.
So I think it's definitely worth doing... but if you're on a home network
and have a router and need port 22 for your local access why not use the
router to transform?
Sean
--
ubuntu-uk@l
Tom Bamford wrote:
> I don't bother changing the server port for sshd, it's security
> through obscurity.
There's nothing wrong with using obscurity to achieve enhanced defence
in depth; running ssh on a non-standard port raises the bar enough to
thwart most automated, background noise brute-force
On Sat, Jan 12, 2008 at 02:33:42PM +, Tom Bamford wrote:
> I don't bother changing the server port for sshd, it's security through
> obscurity.
It's not just that. Some places I go don't allow port 22 (or indeed )
out for ssh purposes. I therefore run sshd on port 443.
Cheers,
Al.
--
Tom Bamford wrote:
> [...]
> I also use FreeNX for remote access to Gnome desktops which doesn't yet
> work properly when you use a different port and block password
> authentication. So I just use Denyhosts to block clients that fail
> authentication, 1 try for the root account and 3 tries for
Alan Pope wrote:
On Sat, Jan 12, 2008 at 12:56:30PM +, Stephen Garton wrote:
Hi Al,
On 12/01/2008, Alan Pope <[EMAIL PROTECTED]> wrote:
On Sat, Jan 12, 2008 at 09:13:56AM +, Stephen Garton wrote:
On a box at home, I have ssh running on a non-specific high numbered
port.
On Sat, Jan 12, 2008 at 01:23:15PM +, Sean Miller wrote:
> I wouldn't waste time on this... as I said, just make the router expose your
> port 22 on your local server on another port to the internet through port
> forwarding. You'll need to also route whatever other ports you want (eg.
> port
On Sat, Jan 12, 2008 at 12:56:30PM +, Stephen Garton wrote:
> Hi Al,
>
> On 12/01/2008, Alan Pope <[EMAIL PROTECTED]> wrote:
> > On Sat, Jan 12, 2008 at 09:13:56AM +, Stephen Garton wrote:
> > > On a box at home, I have ssh running on a non-specific high numbered
> > > port. Is it possible
I wouldn't waste time on this... as I said, just make the router expose your
port 22 on your local server on another port to the internet through port
forwarding. You'll need to also route whatever other ports you want (eg.
port 80) but this would seem a decent solution.
Then everything works and
Stephen Garton wrote:
>
> Sorry, I think I'm lost. Will tomboy sync over ssh when a non-standard
> port is used?
>
From the seems of it - tomboy won't allow non standard ssh ports. You
could work around it by mounting via fuse/sshfs and sync'ing with the
local mount point. However, i'd kee
Hi Al,
On 12/01/2008, Alan Pope <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 12, 2008 at 09:13:56AM +, Stephen Garton wrote:
> > On a box at home, I have ssh running on a non-specific high numbered
> > port. Is it possible to also have it (ssh) listen on port 22, but
> > limit it to computers on t
On Sat, Jan 12, 2008 at 09:13:56AM +, Stephen Garton wrote:
> On a box at home, I have ssh running on a non-specific high numbered
> port. Is it possible to also have it (ssh) listen on port 22, but
> limit it to computers on the local network?
>
Why also have it on 22? Why not just edit ~/.s
On 12/01/2008, Sean Miller <[EMAIL PROTECTED]> wrote:
> Couldn't you use port forwarding on your router?
>
> So have the sshd running on port 22 but expose it to the world at large on
> port, say, 2000 ?
>
> Sean
>
That will do nicely, cheers!
--
Steve Garton
http://www.sheepeatingtaz.co.uk
--
Couldn't you use port forwarding on your router?
So have the sshd running on port 22 but expose it to the world at large on
port, say, 2000 ?
Sean
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/
On a box at home, I have ssh running on a non-specific high numbered
port. Is it possible to also have it (ssh) listen on port 22, but
limit it to computers on the local network?
The reason for asking is that I'd like to do things like synchronise
my tomboy notes over ssh, but there is nowhere in
18 matches
Mail list logo
