Displaying 20 results from an estimated 1000 matches similar to: "[PATCH]: Broken scp -p option"
2003 Apr 21
0
Fix for rcp -r
rcp -r is broken in 4.7 and 4.8. A fix is included below. The
web-based bug interface is currently disabled so I can't open a bug
report. I believe the person that provided the patch to me also
indicated the problem exists in 5.0, but I'm unable to verify that
since I'm only running 4.x. I think they monitor this list so I'll
let them speak up if they choose to.
>--- rcp.c~
2001 May 12
4
Erase the source file open; specify a tempfile name option
I'm curious how to go about submitting a suggestion that affects both
the original BSD version and the portable release. A few days ago I
sent off a BSD-relative patch to openssh at openssh.com. Is this the right
thing to do? I didn't hear anything back, but it's only been 3 days, so
I'm probably just being too antsy.
In the meantime, maybe someone else out there would like to
2000 Aug 18
0
[PATCH] Support symlinks in scp of openssh 2
I'm fond of the "-a" (archive) option of cp, and I'm a heavy user of
scp, so I guess it's inevitable that I would eventually add support
for "-a" to scp. :-) Actually, it's a "-L" flag for preserving
symlinks, and a "-a" flag that is shorthand for "-Lpr".
Please let me know if I'm not doing this right.... I made a great
2005 Oct 11
5
scp bug: newly created dirs do not inherit sgid bit
Dear developers,
I discovered that directories created by scp when recursive
copying into a sgid directory do not inherit the sgid bit. I believe
this is a bug. A patch to fix this is attached.
Regards,
Petr Skovron
-------------- next part --------------
--- scp.c.orig 2005-10-11 16:50:17.000000000 +0200
+++ scp.c 2005-10-11 16:57:25.000000000 +0200
@@ -876,8 +876,12 @@
2002 Jul 13
0
[PATCH]: scp program improved
Hi,
I have made a patch which improves scp utility. It adds two new features:
rate limit and resume support. With rate limit it's possible to limit
transfer speed. Resume allows to continue file transfer where it was last
interrupted. Also the progress meter was improved.
Here is my patch, please send comments about it and what I can do better
if there is something to fix.
---
2001 May 17
6
scp: Problem when source and destination are identical
If the source and destination file are identical, the receiving scp
truncates the file. On the sending end, read() returns 0, and garbage
is sent instead of actual data, and the receiving end puts it into the
file, which at least confuses the users.
--
Florian Weimer Florian.Weimer at RUS.Uni-Stuttgart.DE
University of Stuttgart http://cert.uni-stuttgart.de/
2019 Jan 19
2
Status of SCP vulnerability
Hello,
I would like to request an update of the progress regarding fixes for the recently disclosed SCP vulnerability (CVE-2018-20685, CVE-2019-6111, CVE-2019-6109, CVE-2019-6110)
It has been stated that CVE-2018-20685 has been patched in november but there are currently no information available on the progress of patches regarding the other CVEs.
Will there be a patched release any time soon?
2003 Sep 10
3
[PATCH] No extern declarations of optarg & co if getopt.h is available
Hi,
I have a problem with the extern declarations of optarg, optind, etc.
We're currently moving getopt from being a statically linked function
to a dynamically linked function as part of the Cygwin DLL. On Windows,
this requires to generate special symbols (__imp__optarg, etc.), which
is done by marking the exported variables in the corresponding header.
Instead of
extern char *optarg;
2001 Jan 11
1
Patch to improve -p error message.
Hi all.
I got sick of getting a lame error message when I typed
the wrong thing in for a -p argument, so I wrote
up this patch.
Bad:
% ssh -p L4501 localhost
Secure connection to localhost refused.
Good:
./ssh -p L4501 localhost
Bad port specification 'L4501'.
Mo DeJong
Red Hat Inc
Index: ssh.c
===================================================================
RCS file:
2017 Aug 04
4
Filter files received on scp server
Hey,
So, I would be looking at type A. Forgive me if my understanding of how OpenSSH operates is not reflective of reality. I am assuming that, the file transfer is happening somewhat logically, with a name being known, content written, blah blah.
>From reading scp.c, it appears that, the client end at least knows the file name so I must assume the server end must be given it.
I am hoping to
2017 Mar 27
1
[PATCH v2 09/10] drm/nouveau: Handle frame-packing mode geometry and timing effects
* Frame-packing modes add an extra vtotal raster lines to each
frame above and beyond what the basic mode description calls for.
Account for this during scaler configuration (possibly a bit of a
hack), during CRTC configuration (clearly not a hack), and when
checking that a mode is vaild for a given connector (cribbed from
the i915 driver).
Signed-off-by: Alastair Bridgewater
2010 Nov 19
3
File Offsets for SCP (patch)
I don't know if anyone would be interested in this but I'm including a
patch to allow for offsets when transferring files with SCP.
It's pretty simple and assumes the user knows what they are doing (for
example, if transferring with a wild card the offset would apply to all
files). -A is the number of bytes offset from the beginning of the
files. -Z is the number of bytes inset
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 04/13] Useful debugging
plain text document attachment (lguest64-debug-utils.patch)
This patch contains some nice features used to debug the lguest64 guest.
It has a way to print page tables for either the host or the guest.
It incorporates kallsyms, and can do a nice back trace of a guest
when it crashes. The guest needs kallsyms obviously compiled in.
Note: This code needs to be fixed to be more secure!
Implements
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 04/13] Useful debugging
plain text document attachment (lguest64-debug-utils.patch)
This patch contains some nice features used to debug the lguest64 guest.
It has a way to print page tables for either the host or the guest.
It incorporates kallsyms, and can do a nice back trace of a guest
when it crashes. The guest needs kallsyms obviously compiled in.
Note: This code needs to be fixed to be more secure!
Implements
2006 May 03
1
[LLVMdev] Patch for transform dependencies
Hi,
A number of transforms are actually independent, so here's a partial fix. I
updated the
dependencies in a cluster of transforms: LowerSwitch, Mem2Reg, LowerSelect,
LowerAllocations, UnifyFunctionExitNodes.
The patch has been tested, but not extensively. PassManager doesn't
complain, and
the result of a test pass that requires all these (except for
LowerAllocations) together
works
2009 Aug 23
0
[LLVMdev] x86_64 darwin multilib gfortran testresults
Using the proposed patch for enabling the i386 multilib under the x86_64-apple-darwin
build...
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-August/025040.html
the following gfortran testsuite results are obtained...
Native configuration is x86_64-apple-darwin10
=== gfortran tests ===
Running target unix/-m32
FAIL: gfortran.dg/aint_anint_1.f90 -O (internal compiler error)
FAIL:
2009 Jan 19
2
[LLVMdev] llvm-gfortran test results
The current llvm/llvm-gcc4.2 svn is now fixed with
respect to the extra warnings that were being emitted
by the gfortran compiler. The gfortran testsuite results
under Intel Darwin9 are appended below.
Jack
Native configuration is i686-apple-darwin9
=== gfortran tests ===
Running target unix/-m32
FAIL: gfortran.dg/aint_anint_1.f90 -O (internal compiler error)
FAIL:
2008 Nov 02
1
[LLVMdev] llvm-2.4 prerelease gfortran results
Building the prerelease of llvm-gcc 2.4 on Intel darwin9
with the following patch...
--- llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c.org 2008-10-30 18:55:45.000000000 -0400
+++ llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c 2008-10-30 18:57:29.000000000 -0400
@@ -157,3 +157,27 @@
{
gcc_assert(0);
}
+
+
+bool cvt_utf8_utf16 (const unsigned char *, size_t, unsigned char **,
+
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
This is taken from the work I did on lguest64.
When killing a guest, we read the guest stack to do a nice back trace of
the guest and send it via printk to the host.
So instead of just getting an error message from the lguest launcher of:
lguest: bad read address 537012178 len 1
I also get in my dmesg:
called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f
[<c04069aa>]
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
This is taken from the work I did on lguest64.
When killing a guest, we read the guest stack to do a nice back trace of
the guest and send it via printk to the host.
So instead of just getting an error message from the lguest launcher of:
lguest: bad read address 537012178 len 1
I also get in my dmesg:
called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f
[<c04069aa>]