similar to: [Bug 1600] New: scp(1) man page feedback

channel_new() doesn't free remote_name since 2003/05/11 20:30:25 (git commit b1ca8bb) --- ChangeLog | 4 ++++ channels.c | 3 +-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 4e6b8b2..8f203aa 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +20140323 + - [channels.c] Remove wrong channel_new() comment + channel_new doesn't free

> > Unless you upload a network capture of you mounting and doing the ls -lR > on the client it's hard to say what really goes on. I understand you > might not want to make it public.. but if you do > This is the last thing I'll try after I've exhausted all the other options. How are you mounting your share (which mount options)? > Something weird is going on with

I am creating a database for movies (films) and television shows (shows) that will have has_and_belongs_to_many relationships with the pictures table. CREATE TABLE screenshots ( id serial NOT NULL, filename character varying NOT NULL, content_type character varying NOT NULL, primary key (id) ); CREATE TABLE films ( id serial NOT NULL, name character varying NOT NULL,

Hi everyone, Previous to today my samba install was working fine, after a reboot I wasn't able to access the share and with smbclient the output is as follows: Password: Domain=[RENDER] OS=[Unix] Server=[Samba 3.0.25b-1.1.72-1411-SUSE-CODE10] tree connect failed: NT_STATUS_ACCESS_DENIED There is no firewall in the way, and there is also nothing in the main logs, I do see myself

We have developed a patch that enables changing the SSH window size using the tcp window size as the source. This allows SSH to obtain maximum use of the bandwidth on high BDP links. We also have a page that describes the changes and performance. http://www.psc.edu/~rapier/hpn-ssh/ The patch against CVS is included here. Common subdirectories: src/usr.bin/ssh/CVS and ssh/CVS diff -u

Hi. This functionality was just added in 2.2.0p1. The patch is self-explanatory. Charles --- scp.c.orig-2.2.0p1 Tue Aug 29 19:11:30 2000 +++ scp.c Sat Sep 2 15:14:58 2000 @@ -262,7 +262,7 @@ extern int optind; fflag = tflag = 0; - while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S")) != EOF) + while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S:")) != EOF)

https://bugzilla.mindrot.org/show_bug.cgi?id=1451 Summary: Slight addition to the "scp" man page Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other

Hi, Having learned with difficulties how to retrieve files using scp, I'd like to make a small contribution to the scp man page, i.e.. add a couple of examples on how to copy files to a box and more importantly how to copy them back. Therefore how do I submit my contribution? Regards Dom

Hello, I noticed: 20030124 - (djm) OpenBSD CVS Sync - markus at cvs.openbsd.org 2003/01/23 14:01:53 [scp.c] bandwidth limitation patch (scp -l) from niels@; ok todd@, deraadt@ [...]

As a fairly experienced Unix user, it's obvious to me that scp copies files from left to right -- that is, that the last [host:]file on the command line is the destination. However, this might not be so obvious to users with less experience. It pains me to suggest this, but perhaps the scp man page should be edited to make this more obvious. For example, from the [Free]BSD cp(1) man

As before, it is described on our website. This should apply fairly cleanly to both portable and openbsd ssh. http://www.psc.edu/networking/hpn-ssh/ Only in openssh-3.8.1p1-dynwindow: Makefile diff -u openssh-3.8.1p1/buffer.c openssh-3.8.1p1-dynwindow/buffer.c --- openssh-3.8.1p1/buffer.c 2003-11-21 07:56:47.000000000 -0500 +++ openssh-3.8.1p1-dynwindow/buffer.c 2004-07-12 07:49:29.000000000

Saurabh Nanda via samba <samba at lists.samba.org> writes: > Which implies that the server & client auto-negotiated a protocol version > greater than SMB2.1, right? However, to be sure, I manually specified vers= > in fstab, but something strange happened. While `man mount.cifs` claims > that the following are allowed -- 1.0, 2.0, 2.1, 3.0, 3.1.1 (or 3.11) -- > few of them

Hello, I have noticed that since release 5.x of openssh, the scp command rejects remote user names with white spaces. (We have such user names on Windows hosts) For instance: $ scp myfile "my user"@machine:. used to work with openssh-4.2p1 and fails with 5.2p1 and 5.3p1: my user: invalid user name. I have traced this down to revision 1.129 of scp.c which now calls okname(). OTOH,

I propose a new feature that enables scp to print its status on newlines as well as output to file descriptors that are not terminals. This will allow for more robust logging as well as enable progress parsing for programs such as zenity. The only workaround that I found that does not involve modifying the scp source uses pseudo terminals:

I am using the OpenSSH client (version 5.2p1) in a Linux box L to interact with an embedded SSH server S. When carrying out a recursive transfer from S to L by means of the scp command issued in L (S does not support sftp) the client occasionally prints out a "lost connection" error message at the very end of the transfer. After some debugging I found out that the error message (as

Hello, I''m developing an app that basically, receives a 10MB or less XLSX files with +30000 rows or so, and another XLSX file with about 200rows, I have to read one row of the smallest file, look it up on the largest file and write data from both files to a new one. I just did a test reading a few rows from the largest file using ROO (Spreadsheet doesn''t support XSLX and

[Mod: header changed -- alex] ###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

> > When you provide an exact vers= then no auto-negotiation happens (unless > you pass "vers=3" which essentially means 3.x: use 3.0 or above). You > either get the connection or mount fails. None the less, you can dump > the current SMB ressources managed by the kernel by looking at > /proc/fs/cifs/DebugData if your kernel is recent enough it should show > the SMB

Hi, can't seem to login to Samba Server using notebook. OS is FreeBSD 10.3. Samba Version is 4.6.6 Connect to the remote Samba server using L2TP/IPSec connection. When trying to login it's not accepting the correct credentials. When ssh'ing to the server can login without any issue: # smbclient -Uusername //server/share Enter SERVERNAME\username's password: Domain=[DOMAINNAME]