Talk:SSH, limiting to SCP or Rsync only
From FreeBSDwiki
(Difference between revisions)
(pretty clearly a characterset problem) |
|||
| 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) |
Revision as of 14:20, 22 October 2007
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.
--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?
--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. --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. --Jimbo 15:20, 22 October 2007 (EDT)
