Talk:SSH, limiting to SCP or Rsync only - Revision history

Jimbo: moved Talk:SSH: Limiting to SCP or Rsync only to Talk:SSH, limiting to SCP or Rsync only

2010-01-16T14:38:23Z

moved Talk:SSH: Limiting to SCP or Rsync only to Talk:SSH, limiting to SCP or Rsync only

Ice: /* Security aspect */

2007-11-04T10:06:03Z

Security aspect

Ice: security concern with scpftprsynconly

2007-11-04T09:51:42Z

security concern with scpftprsynconly

Jimbo at 19:21, 22 October 2007

2007-10-22T19:21:57Z

Jimbo at 19:20, 22 October 2007

2007-10-22T19:20:21Z

Jimbo: pretty clearly a characterset problem

2007-10-22T19:17:40Z

pretty clearly a characterset problem

Dave: just guessing, really

2007-10-22T17:41:23Z

just guessing, really

Dave at 16:25, 22 October 2007

2007-10-22T16:25:19Z

New page

==just btw==
# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
scpsftprsynconly.c: In function â€˜mainâ€™:
scpsftprsynconly.c:48: error: expected â€˜)â€™ at end of input
scpsftprsynconly.c:48: error: expected declaration or statement at end of input
#

tried running this on a centos box and this is what I'm getting. dubl-U Tee Eff Mmm8.

--[[User:Dave|Dave]] 12:25, 22 October 2007 (EDT)

@@ Line 38: / Line 38: @@
 You should probably not rely on scpftprsynconly to PREVENT users from executing programs on your machine,
   ./scpsftprsynconly foo 'scp -S givemeshell asd asd:asd'
-Will execute the givemeshell command with some obscure arguments. I haven't tried it with scpftprsynconly installed as a shell but it should be as easy as
+Will execute the givemeshell command with some obscure arguments. To get a shell with this inplace, upload a script/program that reverse connect or what you want then just:
-  ssh foohost 'scp -S givemeshell'.
+  ssh foo@barhost "scp -S echo asd asd:asd"
 Probably should mention this in the article..
 --[[User:Ice|Ice]] 04:51, 4 November 2007 (EST)

← Older revision		Revision as of 09:51, 4 November 2007
Line 34:		Line 34:

	The problem you were having was that a good samaritan who manually edited the article to remove spam accidentally damaged the code a while back. I looked through history on the article and reverted to prior to the damage. --[[User:Jimbo\|Jimbo]] 15:20, 22 October 2007 (EDT)		The problem you were having was that a good samaritan who manually edited the article to remove spam accidentally damaged the code a while back. I looked through history on the article and reverted to prior to the damage. --[[User:Jimbo\|Jimbo]] 15:20, 22 October 2007 (EDT)
		+
		+	== Security aspect ==
		+	You should probably not rely on scpftprsynconly to PREVENT users from executing programs on your machine,
		+	./scpsftprsynconly foo 'scp -S givemeshell asd asd:asd'
		+	Will execute the givemeshell command with some obscure arguments. I haven't tried it with scpftprsynconly installed as a shell but it should be as easy as
		+	ssh foohost 'scp -S givemeshell'.
		+
		+	Probably should mention this in the article..
		+
		+	--[[User:Ice\|Ice]] 04:51, 4 November 2007 (EST)

@@ Line 31: / Line 31: @@
 --[[User:Dave|Dave]] 13:41, 22 October 2007 (EDT)
-== pretty clearly a characterset problem ==
+== somebody oopsed on a kill-the-spam edit ==
-I dunno what you're cutting and pasting with, but I suggest you use a command line tool.  That AE crap is charset problem all the way.  --[[User:Jimbo|Jimbo]] 15:17, 22 October 2007 (EDT) edit: nm, that's a charset problem from pasting HERE not vice versa.  The problem you were having was that a spammer damaged the code a while back.  I looked through history on the article and reverted to prior to the damage.  --[[User:Jimbo|Jimbo]] 15:20, 22 October 2007 (EDT)
+The problem you were having was that a good samaritan who manually edited the article to remove spam accidentally damaged the code a while back.  I looked through history on the article and reverted to prior to the damage.  --[[User:Jimbo|Jimbo]] 15:20, 22 October 2007 (EDT)

← Older revision		Revision as of 19:20, 22 October 2007
Line 33:		Line 33:
	== pretty clearly a characterset problem ==		== pretty clearly a characterset problem ==

−	I dunno what you're cutting and pasting with, but I suggest you use a command line tool. That AE crap is charset problem all the way. --[[User:Jimbo\|Jimbo]] 15:17, 22 October 2007 (EDT)	+	I dunno what you're cutting and pasting with, but I suggest you use a command line tool. That AE crap is charset problem all the way. --[[User:Jimbo\|Jimbo]] 15:17, 22 October 2007 (EDT) edit: nm, that's a charset problem from pasting HERE not vice versa. The problem you were having was that a spammer damaged the code a while back. I looked through history on the article and reverted to prior to the damage. --[[User:Jimbo\|Jimbo]] 15:20, 22 October 2007 (EDT)

← Older revision		Revision as of 19:17, 22 October 2007
Line 30:		Line 30:

	--[[User:Dave\|Dave]] 13:41, 22 October 2007 (EDT)		--[[User:Dave\|Dave]] 13:41, 22 October 2007 (EDT)
		+
		+	== pretty clearly a characterset problem ==
		+
		+	I dunno what you're cutting and pasting with, but I suggest you use a command line tool. That AE crap is charset problem all the way. --[[User:Jimbo\|Jimbo]] 15:17, 22 October 2007 (EDT)

← Older revision		Revision as of 17:41, 22 October 2007
Line 10:		Line 10:

	--[[User:Dave\|Dave]] 12:25, 22 October 2007 (EDT)		--[[User:Dave\|Dave]] 12:25, 22 October 2007 (EDT)
		+
		+	== just guessing, really ==
		+
		+	since I don't know shit, but I added a } before the #ifdef DEBUG section and now I'm getting:
		+
		+	[root@web ~]# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
		+	scpsftprsynconly.c:45: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
		+	scpsftprsynconly.c:49: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
		+	[root@web ~]#
		+
		+	which is in the first lines of
		+	if (argc < 3) {
		+	printf (restrictmsg);
		+	return 1;
		+	}
		+	if ((strncmp (argv [2], "scp ", 4) != 0)
		+
		+	wha?
		+
		+	--[[User:Dave\|Dave]] 13:41, 22 October 2007 (EDT)