similar to: Patch for scp (openssh 1.2.2p1)

Hi, we are using usernames on our systems that contain a point '.', like "r.john". We found it necessary to patch the source to make the "scp" command work with those usernames. Cheers Kai --- openssh-2.2.0p1/scp.c Wed Aug 30 01:11:30 2000 +++ withpoint/scp.c Mon Dec 11 02:06:35 2000 @@ -1042,7 +1042,7 @@ c = *cp; if (c & 0200) goto bad; - if

Ok, here is the patch again... I also included fixes for the bits that originally gave my mailer fits... Two votes for orange, so I went with orange... Doing diffs in .: --- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800 +++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800 @@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char * Result +=

In several places, openssh-2.9.9p2 passes a 'char' value to a ctype macro like 'isdigit'. This has undefined behavior on hosts with signed characters, if the character value happens to be negative. For example, isdigit('\200') expands to an array access that is a subscript error on hosts with signed characters where '\200' == -128. This leads to incorrect results,

http://bugzilla.mindrot.org/show_bug.cgi?id=377 Summary: Reduce compiler warnings. Use unsigned args to the ctype.h is*() macros. Product: Portable OpenSSH Version: -current Platform: Sparc OS/Version: Solaris Status: NEW Severity: trivial Priority: P2 Component: Miscellaneous

Hi OpenSSH developers In the source file *scp.c* there is a function called *okname(char *cp0)* that validates the entered username by using the scp command as follows: * *[ Fragment scp.c start ] ... int okname(char *cp0) { int c; char *cp; cp = cp0; do { c = (int)*cp; if (c & 0200) goto bad; if (!isalpha(c) &&

Why does the local scp determine what characters are valid in a remote host userid? A friend of mine just had his ISP convert him to using a userid of the form 'user#isp-acct' (eg, "ssh -l 'joe#foo.org' foo.org" is used to login). The OpenSSH ssh and sftp commands both allow this form of userid. However, it seems that scp has its very own idea of what characters are

Hi a fellow debian developer pointed it out to me, that ssh itself does not check the username that is provided for login into a remote host, but that scp checks it. I could verify that the current openssh code from cvs still has a check for the username in scp.c but not in ssh.c. So I created the attached small patch to remove the username check from scp. I hope ?t's correct and that you

I installed OpenSSL 0.9.5 in the default location (/usr/local/ssl) on my Solaris 2.7 box, and then tried to install OpenSSH 1.2.2p1. Configure (with no arguments) complains that it can't find working OpenSSL libraries. The last few lines of config.log show a whole bunch of attempts to compile the test code, all failing of course. My /usr/local/ssl DOES have an include/openssl directory

Hi, openssh-1.2.2p1 seems to have 2 problems on ipv6 (and ipv4 mapped addresses). 1. "BREAKIN ATTEMPT" warnings from ipv4 node 2. X forwarding The following patche fixes them. Thanks. diff -ru openssh-1.2.2p1/canohost.c openssh-1.2.2p1-20000308/canohost.c --- openssh-1.2.2p1/canohost.c Fri Jan 14 13:45:48 2000 +++ openssh-1.2.2p1-20000308/canohost.c Wed Mar 8 00:25:18 2000 @@

Hi there, I'm using the latest stable release of open-ssh, and scp, and am having a problem... I want to use scp to backup some important files on a publically visible server. Everything seems fine, except for two details: 1) scp will not copy a core file. This server is used for devel, and the occasional core file is created. scp almost always coughs on such files, and stops. 2) scp -r

I tracked down a problem related to running fortune at the start of every shell instance and scp. I imagine the problem would be the same with any utility automatically started upon login that prints to the screen. I am not sure if this intentional, a bug or just an annoyance that one should not run such utilities at login. Maybe one for the faq eh, so no one respends the time I just did

Me again, Here's a patch to fix ctypes. There was an off-by-one correction that looks like it isn't needed. Boundary conditions and single-entry items, like isspace(), now work for me. mh -- Martin Hicks Wild Open Source Inc. mort@wildopensource.com 613-266-2296 # This is a BitKeeper generated patch for the following project: # Project Name: The kernel C library

This is needed as the basis for the readlink -f option. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- v2: Don't implement the BSD/GNU extension of allowing a non-existent last part. Use open(O_PATH) and procfs to get resolved name from the kernel. --- a/usr/include/stdlib.h +++ b/usr/include/stdlib.h @@ -92,4 +92,6 @@ static __inline__ int grantpt(int __fd) return

Dear llvmers, I decided to write my own scripts to compile the SPEC programs, and they work fine, except with 403.gcc. Basically, I take the file 403.gcc.linked.rbc from the ...\Output folder that the LLVM test suite produces. Then I use this linked.rbc file to generate an executable file via the following commands: llc 403.gcc.linked.rbc -o 403.gcc.linked.s clang 403.gcc.linked.s -o

I recently built openssh 2.1.1p1, under solaris. I noticed that I had problems running scp. It seems that it could not find the executable on the remote end. This was odd, becuase it existed in /usr/local/bin, publically executable, and /usr/local/bin/was in the users' normal PATH (exported, even). So finally, I twiddled the source to make it call /usr/local/bin/scp, instead of just

In 0.97 io.h is wrong in several places. it should be returning __v, not v. static __inline__ unsigned char inb(unsigned short __p) { unsigned char __v; asm volatile("inb %1,%0" : "=a" (__v) : "dN" (__p)); return v; } How do I get rid of these warnings? /home/mesa/boot/klibc/klibc/include/stdlib.h:21: warning: shadowing built-in function `abs'

This is needed as the basis for the readlink -f option. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- --- a/usr/include/stdlib.h +++ b/usr/include/stdlib.h @@ -92,4 +92,6 @@ static __inline__ int grantpt(int __fd) return 0; /* devpts does this all for us! */ } +__extern char *realpath(const char *, char *); + #endif /* _STDLIB_H */ --- a/usr/klibc/Kbuild +++

Commit-ID: 32b36eb98fafad924f3f69904d74d2f2168a4753 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=32b36eb98fafad924f3f69904d74d2f2168a4753 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 01:08:47 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:48:43 -0800 [klibc] Implement realpath() This

Full_Name: JinNyong Huh Version: 2.6.1 OS: Linux(SUSE-9.0) Submission from: (NULL) (220.75.209.235) ROracle Packages is not to be installed in my Linux. The enviroments are as follows: * O/S Profile [ export ORACLE_BASE=/opt/oracle export ORACLE_SID=DEMO10G export ORACLE_HOME=$ORACLE_BASE/product/10g export ORACLE_DOC=$ORACLE_HOME/doc export ORACLE_TERM=vt220 export TERM=vt100 export

Hi, stevesk at sweden.hp.com wrote: > Has any progress been made on this issue? I've included an older > message that has a stack trace, which if I recall was still the same in > 2.1.1p1. I can provide a newer trace or additional information if > needed. not really... On a non-trusted system with HP AnsiC it seems to work if changing shutdown(fdin, SHUT_WR) to shutdown(fdin,