Hello;
OK, this may make more than a few of you cringe, but here goes:
I am having difficulties setting up ssh (ossh4.3p2 with PAM-enabled - NIS
-Solaris8/Sparc) to authenticate and allow users passwordless entry based
solely on one or more of the following:
1. User is a member of an NIS 'gr
Mike,
Here is the solution. Apparently this is a particular problem with
slackware 10.0...
http://www.pocketace.net/pocketace.php?pg=articles&ar=slackware)
(excerpt)
"The Slackware udev.rules included with Slackware 10 needs to be altered
for the man, less and ssh commands to work properly. To f
This older version of SCO doesn't support PAM.
However, I was able to finally get this working. Basically the issue was
that the configure.ac file had defined DISABLE_SHADOW, but we are indeed
using shadow passwords. I caught this early on but if I removed this
definition I could never get ssh to
No, don't use xhost +
The entire point of using ssh for X11 forwarding is that the ssh
connection comes from a local process - you don't have to accept
outside X11 connections.
xhost + is used specifically for accepting X11 connections that
_don't_ come from a local process (e.g not over your SSH
I have a working VPN tunnel between Linux boxes working great! I am
tunneling between the networks using the TUN interfaces which is quick,
simple, secure, and easy.
However, I have a need to use this for windows laptops on the go. This
means that a Linux box running as a gateway for the client i
Mark Holden wrote:
Thanks everyone for the help! I will definitely check all of these out.
I've started with trickle and have successfully limited the bandwidth in
the data transfer from the local machine to the remote backup server
using the command as given by Igor (limiting, for now, at 5 MB
Hi François, yes i have the options below in my /etc/ssh/sshd_config
AllowTcpForwarding yes
GatewayPorts yes
I ran out of ideas where could be the problem...
Thanks anyway and i still apreciate some tips.
I dont want to use xhost because of security problems.
nader
> You need to also have this l
Let me be the first (of probably many) to say this...
Don't.
This opens up a gaping security hole, and won't help one iota with SSH
tunneling.
-Original Message-
From: Jason Mitchell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 18, 2006 5:20 PM
To: [EMAIL PROTECTED]
Cc: secureshell@se
For the sake of all who have been following this thread, and anyone who
may experience this problem in the future, this appears to be an issue
with the default udev.rules on slackware. Now, I am off to figure out
what needs to be changed. Thanks to all who responded. Here are the
helpful URLs wh
Use xhost +;ssh -l
once you are done use xhost -;
./thanks
ilaiy
On 4/18/06, Nader Amadeu <[EMAIL PROTECTED]> wrote:
> Hi all, I've googled for more than a week trying to
> fix this SSH X11 tuneling problem.
> I appreciate some help and thank you in advance.
>
> I have a remote Solaris 9 with
Yes. I am completely at a loss. The Linux kernel version I updated to
is 2.6.15.3. After chmoding 666 on /dev/tty, I changed it back to 777
because it is definitely a directory. Evidence below:
[EMAIL PROTECTED]:/dev/tty# ls -l
total 0
crw--- 1 root root 3, 10 2007-03-21 00:58 s
crw--
11 matches
Mail list logo
