similar to: [draft PATCH] whitelist support for refuse options

Displaying 20 results from an estimated 900 matches similar to: "[draft PATCH] whitelist support for refuse options"

2020 Aug 03
6
Deprecation of scp protocol and improving sftp client
I hear you - but it seems that the choice is between (a) limiting "scp" functionality to address the security vulnerability, and (b) killing "scp" altogether. I'd much prefer (a), even if it means I lose "scp remotehost:foo\* .". Especially, since (almost always) I have equal privileges on both local and remote hosts, so in that case I just originate that
2014 Jan 10
1
samba 4.1.3 -- multiple bugs & 1, 297 coredumps -- coredump backtrace + full-backtrace included
Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1
2004 Feb 04
1
Signal 11 in smbd 3.0.2rc2 on printer operation!
Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
Hi, We are having issues with our samba server running on CentOS 7. It's generating core dumps and dumping them in the / (root filesystem) directory in the form of core.##### where the # is a series of numbers. Snippets of log files and some troubleshooting commands are below. Hope someone can have a look and see if I should file this as a bug, as there were similar posts in the samba
2002 Sep 10
0
[PATCH] Add --preserve-atime switch to rsync
In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***
2004 Feb 20
1
[patch] fix for "refuse options" ignored due to popt
Hello, I found the reason why "refuse options" is ignored on the server side. When then 5th argument (int val) in the poptOption struct is set to zero, the parsing function poptGetNextOpt() just continues with the next arg, without returning. So check_refuse_options() is simply not called in such cases. The attached patch makes "refuse options" work with checksum and
2013 Jun 03
1
Adding arguments to the options
Hello, I am developing an application which uses the Rsync. I have added an option for HTTPS in rsync code like '-v' for "--verbose". But now I want to make that option to take the arguments. For that in options.c file, I have added the entry in the array of structure as, > static struct poptOption long_options[] = { > /* longName, shortName, argInfo, argPtr, value,
2006 Mar 14
4
has_one
I''ve got an order model that stores order data. One piece of data is a credit card type, which is a digit 1,2 or 3. I have a cardType model that has an id, shortName and LongName for the credit card merchant (visa, mastercard, amex). I want to be able to say: order.cardType.shortName, but can''t seem to get has_one working. It works with has_many and a finder_sql statement on
2011 Apr 22
1
[LLVMdev] Compile-time evaluation of functions
On Thu, Apr 21, 2011 at 2:43 PM, Eric Christopher <echristo at apple.com>wrote: > > On Apr 20, 2011, at 4:34 PM, Talin wrote: > > > Also, looking in the SVN repo, it appears that some of the files in > include/llvm/ExecutionEngine have not been touched in a long time, and that > scares me a bit - what's the current state of the LLVM interpreter? > > > >
2008 Apr 07
3
rsync installation _error exit code1
Skipped content of type multipart/alternative-------------- next part -------------- # ./configure configure.sh: Configuring rsync 3.0.1 checking build system type... hppa2.0w-hp-hpux11.11 checking host system type... hppa2.0w-hp-hpux11.11 checking target system type... hppa2.0w-hp-hpux11.11 checking for gcc... no checking for cc... cc checking for C compiler default output file name... a.out
2004 May 27
0
compiling on HP-UX
Hi, everybody here! I hope not all is old stuff, because I only scanning subjects fast in this list. (and sorry for my worse english, too.) 1) rsync 2.6.0 on HP-UX (HP-UX server B.11.00 U 9000/803) Running as server: crashed always after receiving data. The data is transmitted correctly, and the server dies afterwards. (rsync2.5.7 works anyway) (about rsync2.6.2 later) 2) compiling
2020 Oct 21
6
"Semi-Trusted" SSH-Keys that also require PAM login
Hello all, in order to connect to my SSH servers from untrusted devices like company computers or my smartphone, I set up 2FA with google-authenticator hooked into PAM. However, this is not really 2FA at least for the smartphone, since I use the same device for generating the TANs and it is also at least inconvenient to always require a new TAN for each connection. I do not want to solely rely
2020 Feb 11
0
[draft PATCH] whitelist support for refuse options
Hi Nick, Just in case you aren't already aware of it, there is a tool that limits rsync to particular directories: rrsync - Restricts rsync to subdirectory declared in .ssh/authorized_keys https://www.samba.org/ftp/unpacked/rsync/support/rrsync There is also a generic tool (I wrote this one) for limiting incoming ssh commands to a fixed list of specific actual commands (with
2003 Jul 06
3
New wildmatch code in CVS
If you've been watching CVS, you may have noticed that I checked in some new files named wildmatch.c and wildmatch.h. This code implements the shell-style wildcard matching with rsync's extension that "**" matches a "/" but "*" and "?" does not. I have also checked in a new test module which has allowed me to test a few things on all the machines
2004 Jan 07
1
BUG in 2.6.0: make test failes if build dir is not source dir
There is a small bug in the build system of 2.6.0: If the directory you build rsync in differs from the sourcedir "make test" failes: $ tar -xzf ~/rsync-2.6.0.tar.gz $ mkdir build $ cd build $ ../rsync-2.6.0/configure .... $ make test .... PASS unsafe-byname PASS unsafe-links ----- wildmatch log follows Testing for symlinks using 'test -h' + /tmp/bla/build/wildtest Unable
2003 Jul 05
1
make check's diff -u vs -c
Wayne, i like the diff -u idea. I find -c awkward. It seems to me that the shell script could test for support of -u and if present use it instead of -c. ala if [ -n "`diff -u /dev/null /dev/null 2>&1`" ] then difftype="-c" else difftype="-u" fi diff $difftype "$2"/"$f" "$3"/"$f" || failed=YES or something
2018 May 21
2
Getting variable names from LLVM Pass
Hi, I want to retrieve the variable names used in a statement, I tried the following snippet, but it only gives me the variable named in llvm bitcode. I need the variable name in source code. for (auto op = I.op_begin(); op != I.op_end(); op++) { Value* v = op->get(); StringRef name = v->getName(); } Is there specific documentation I can
2003 Oct 08
2
2.5.6: a number of minor issues
I just picked up rsync 2.5.6 and installed it. I haven't actually _used_ it for anything yet; this is entirely about a handful of minor issues I noticed while building it. You may care or you may not; for simplicity of language (to avoid many repeated "in case you care" and such), the text below is written assuming you care about them all. On a (32-bit) SPARC system, I noticed:
2018 May 21
0
Getting variable names from LLVM Pass
> On 21 May 2018, at 18:38, Ridwan Shariffdeen via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > I want to retrieve the variable names used in a statement, I tried the following snippet, > but it only gives me the variable named in llvm bitcode. I need the variable name in source code. > > for (auto op = I.op_begin(); op != I.op_end(); op++) { >
2024 Jul 03
4
Request for a Lockdown option
Dear OpenSSH developers, Thanks a lot for your work on OpenSSH. We use it a lot and it is very helpful for our daily work. Would it be possible to have a lockdown option as a workaround in case of a remotely exploitable problem in ssh. This may help react to compromised keys/passwords, configuration issues, software bugs or other problems for example when Debian broke ssh . My Idea would be