In message <[EMAIL PROTECTED]> Doug Ambrisko writes:
: Another alternative is to remove the setuid bits /usr/bin/ssh and
: then do a "runsocks ssh".
That's not really an option for my work patterns...
: I could do the work if deemed usefull. I don't want to maintain
: my own branch and we use t
> : I'd like to get this committed - I'll try and take a look at it tonight,
> : time permitting. I would definitely like to allow SSH to work with dante,
> : though, since that's a better (BSDL) alternative than the restricted NEC
> : version.
I don't know well about dante, but if it is one of s
James E. Pace writes:
|
| I rebuilt -current on Friday, and OpenSSH does not work through a
| SOCKS firewall.
|
| In my make.conf, I have "USE_SOCKS= YES", which is used in the
| ports/security/ssh port.
As mentioned we have ssh in the base system so your are picking that up.
Another alternativ
In message <[EMAIL PROTECTED]> Kris Kennaway
writes:
: On Mon, 6 Mar 2000, Warner Losh wrote:
:
: > Sure. Here's what I have in my uncommitted tree. It assumes that you
: > have socks installed already. Known to work with the nec port, not
: > known one way or the other on dante.
: >
: > Oh,
On Mon, 6 Mar 2000, Warner Losh wrote:
> Sure. Here's what I have in my uncommitted tree. It assumes that you
> have socks installed already. Known to work with the nec port, not
> known one way or the other on dante.
>
> Oh, there's lots of warnings from this, but it does work.
I'd like to
In message "James E. Pace" writes:
: I rebuilt -current on Friday, and OpenSSH does not work through a
: SOCKS firewall.
:
: In my make.conf, I have "USE_SOCKS= YES", which is used in the
: ports/security/ssh port.
:
: Any help?
Sure. Here's w
I rebuilt -current on Friday, and OpenSSH does not work through a
SOCKS firewall.
In my make.conf, I have "USE_SOCKS= YES", which is used in the
ports/security/ssh port.
Any help?
Thanks,
James
This letter brought to you by: *
**