> On Sat, 2010-08-28 at 01:22 +0100, Daniel Case wrote:
> > Hi there,
> >
> > One of my servers has recently been attacked, it has one remote SSH
> > user which cannot run 'sudo', i made it like that so that if it was
> > comprimized, no-one would be able to do much.
> >
> > However, someone mana
Yes, you can do it. Basically, you want to set up a "local port" and a
"remote port". I don't have a windows box in front of me, but it's under
tunneling somehwere. You can create SSH keys for windows boxes using the
putty keygen tool.
-g
On 28/08/10 19:46, Jacob Mansfield wrote:
> any way t
any way to do that through putty?
On 28 August 2010 18:13, Alan Lord (News) wrote:
> On 28/08/10 17:37, Matthew Macdonald-Wallace wrote:
> > If the VNC Server is on the same machine that you are ssh'ing into,
> > then the command would look as follows:
> >
> > ssh -C -L 5900:localhost:5900@ -N&
On 28/08/10 17:37, Matthew Macdonald-Wallace wrote:
> If the VNC Server is on the same machine that you are ssh'ing into,
> then the command would look as follows:
>
> ssh -C -L 5900:localhost:5900@ -N&
We do this to manage some of our customers' servers. We also use
private/public key pairs, an
Quoting Jacob Mansfield :
> how do I do that?
Assuming that both machines (the VNC Client and the VNC Server) are
running Linux and the VNC server is on port 5900, then run the
following command:
ssh -C -L 5900::5900 @ -N &
Then setup your vnc client to connect to port 5900 on localhost.
I
how do I do that?
On 28 August 2010 15:30, Matthew Macdonald-Wallace <
matt...@truthisfreedom.org.uk> wrote:
> Quoting Jacob Mansfield :
>
> > I have vnc to my servers, but it's locked down to my work and internal
> home
> > addresses only using firestarter. would this be an option for you?
>
> T
Quoting Jacob Mansfield :
> I have vnc to my servers, but it's locked down to my work and internal home
> addresses only using firestarter. would this be an option for you?
Tunnel the VNC over ssh - it's more secure and it makes it much harder
for someone to sniff the traffic.
M.
--
Matthew M
I have vnc to my servers, but it's locked down to my work and internal home
addresses only using firestarter. would this be an option for you?
On 28 August 2010 15:24, Matthew Macdonald-Wallace <
matt...@truthisfreedom.org.uk> wrote:
> Quoting "K.de Jong" :
>
> > If ssh is rarely used
> > and you
Quoting "K.de Jong" :
> If ssh is rarely used
> and you have a running webserver
> you could consider using ajaxterm
>
> you only listen to ssh on localhost
> and have website that allows access to ssh
>
> this is slower and does not work well with remote ssh auth keys
> but just another solution.
If ssh is rarely used
and you have a running webserver
you could consider using ajaxterm
you only listen to ssh on localhost
and have website that allows access to ssh
this is slower and does not work well with remote ssh auth keys
but just another solution.
and
port knocking
it opens access to
On Saturday 28 Aug 2010 08:05:03 Matthew Daubney wrote:
> Denyhosts is quite useful in stopping brute force attacks. After so many
> failed attempts it just blocks the attacking IP.
See also fail2ban, which is in my opinion more useful. It works using
iptables, and supports all kinds of brute-for
You can't hide /etc/passwd because that's how the system translates
userids into usernames (and thus how the system understands whether a
user has access to a specific file or not)
What you might consider is using non-password authenticated SSH
sessions-- you can do this in /etc/sshd/sshd_con
Quoting Daniel Case :
> Hi there,
>
> One of my servers has recently been attacked, it has one remote SSH user
> which cannot run 'sudo', i made it like that so that if it was comprimized,
> no-one would be able to do much.
Switch to using keys instead of passwords, that way you can lock down
w
On Sat, 2010-08-28 at 01:22 +0100, Daniel Case wrote:
> Hi there,
>
> One of my servers has recently been attacked, it has one remote SSH
> user which cannot run 'sudo', i made it like that so that if it was
> comprimized, no-one would be able to do much.
>
> However, someone managed to gain the
On 28 August 2010 01:22, Daniel Case wrote:
> I need to know mainly how to stop the SSH user running su in the first place
> and how to stop the user seeing files like /etc/passwd
You could always rename su to something else, I suppose... I renamed
"wget" to "webget" on one server because scripts
Hi there,
One of my servers has recently been attacked, it has one remote SSH user
which cannot run 'sudo', i made it like that so that if it was comprimized,
no-one would be able to do much.
However, someone managed to gain the password to that account on the server
then used "vi /etc/passwd" to
16 matches
Mail list logo
