Displaying 3 results from an estimated 3 matches for "auth_restricted".
2003 Jan 29
0
[PATCH] features for restricted shell environments
...T,
VEERING NORTHEASTERLY 5 LATER. WINTRY SHOWERS. GOOD.
--- auth-options.c 28 Jan 2003 18:06:50 -0000 1.1.1.2
+++ auth-options.c 29 Jan 2003 20:39:19 -0000 1.7
@@ -133,7 +135,7 @@
goto next_option;
}
cp = "environment=\"";
- if (options.permit_user_env &&
+ if (!auth_restricted(RESTRICT_ENV, pw) &&
strncasecmp(opts, cp, strlen(cp)) == 0) {
char *s;
struct envstring *new_envstring;
@@ -217,8 +219,6 @@
}
cp = "permitopen=\"";
if (strncasecmp(opts, cp, strlen(cp)) == 0) {
- char host[256], sport[6];
- u_short port;
char...
2004 Jan 19
3
Security suggestion concering SSH and port forwarding.
Hi,
sorry if it is the wrong approuch to suggest improvments to OpenSSH,
but here comes my suggestion:
I recently stumbled upon the scponly shell which in it's chroot:ed form is
an ideal solution when you want to share some files with people you trust
more or less.
The problem is, if you use the scponlyc as shell, port forwarding is still
allowed. This can of course be dissallowed in
2003 Feb 17
2
Limit forwarding to specific ports
Hello,
We are using the AllowUsers feature of sshd and would like to control
which users can ask for forwarding of which ports. E.g. when the
user is foo, allow him to tunnel connections to bar:5678 and baz:7654,
but no shell (or some dummy shell) and no other forwardings.
Is such feature planned for the future? Would you accept such patch
in the mainstream distribution?
I would appreciate Cc: