similar to: OpenSSH 3.4p1's top level .cvsignore file

if i want to learn more about implementing a /dev/urandom, where would be a good place to start? thanks, wendy -- wendy palm Cray OS Sustaining Engineering, Cray Inc. wendyp at cray.com, 651-605-9154

simon- any luck with that GSS-API patch for 3.6.1? ben/markus/whoever - will this ever be added to source? thanks, wendy -- wendy palm Cray OS Sustaining Engineering, Cray Inc. wendyp at cray.com, 651-605-9154

It would be nice if the CVS source had a .cvsignore file in the main dir with the following items: ssh scp sshd ssh-add ssh-keygen ssh-keyscan ssh-agent sftp-server sftp configure config.h.in config.h config.status Makefile ssh_prng_cmds *.out Plus a .cvsignore file in openbsd-compat that ignored "Makefile". ..wayne..

do_pre_login() in session.c is used (in do_exec_pty()) before it's declared, which is causing some problems for me. please move it up a couple hundred lines in the file. patch included for 0807 snapshot. thanks, wendy % diff -u session.c.orig session.c.mod --- session.c.orig Tue Aug 7 13:11:51 2001 +++ session.c.mod Tue Aug 7 16:21:07 2001 @@ -397,6 +397,34 @@ } }

I have noticed that the contents of per-directory .cvsignore files apply outside their subtrees when using --cvs-exclude in rsync 2.6.0. In the results below, notice how dir1/.cvsignore is applying to a file in dir2. There is no ~/.cvsignore, and the CVSIGNORE variable is unset. % ls -AFR .: dir1/ dir2/ ./dir1: .cvsignore file1 ./dir2: file2.foo % cat dir1/.cvsignore *.foo % /usr/bin/rsync

we are encouraging the use of protocol 2 over protocol 1, correct? but ssh's default is that protocol 1 is tried first, then protocol 2. this can be overridden in the ssh_config file and by command line options, of course, but shouldn't we set the default to be what we want users to use? thanks, wendy -- wendy palm Cray OS Sustaining Engineering, Cray Inc. wendyp at cray.com,

i have a site that needs to increase the socket buffer size. this is something i really don't know much about, myself. they need to increase it to at least 300k to get decent performance (specifically for scp). what is the current default & are there any known ramifications to increasing it? thanks, wendy -- wendy palm Cray OS Sustaining Engineering, Cray Inc. wendyp at cray.com,

Hi: Just did my first svn checkout. Pretty painless. I noticed that icecast and each of its dependent modules (except m4) has a .cvsignore file. Am I right in thinking these are redundant now? Geoff. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

Here a bug report about "!" not working properly in 2.6.4 and above, paraphrased... > Ok, see attachment. I've tested it right now between two hosts > running rsync 2.6.3-2 and 2.6.6-1. It works in the forward direction, > backwards it gives > > '!' rule has trailing characters: ! > rsync error: syntax or usage error (code 1) at

does anyone have a comment to make about this? (cert picked it up and we're being asked for a vendor response) http://www.securityfocus.com/archive/1/324016/2003-06-03/2003-06-09/0 do we have an "official" response yet? thanks, wendy -- wendy palm Cray Open Software Development, Cray Inc. wendyp at cray.com, 651-605-9154

When we were porting OpenSSH on SX, we had similar problem. And when we did #undef HAVE_B64_NTOP in config.h, we faced linking problem as b64_pton() multiply defined, in base64.c and in libc.a. So we modified configure to check both the functions b64_pton() and b64_ntop(). But we gave priority to native function if available. Following are the diffs of three files we changed 1. configure (line

http://bugzilla.mindrot.org/show_bug.cgi?id=366 Summary: .cvsignore shouldn't be in distrib Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

https://bugzilla.samba.org/show_bug.cgi?id=1873 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From wayned@samba.org 2004-10-05 17:19

is anyone running, or advocating running openssh in combination with dce? what would be the concerns? on first glance, i'd say they shouldn't be run together, but i don't know enough about dce to be able to definitively state that. thanks, wendy -- wendy palm Cray OS Sustaining Engineering, Cray Inc. wendyp at cray.com, 651-605-9154

memset has apparently been fixed in unicos afterall, or else the current code straightened out whatever was going wrong. i'm not sure what happened, but deattack.c changes are no longer necessary. i'm not going to look a gift horse in the mouth.... crays run great straight out of the box for 3.5p1 as released. sorry for the long delay in replying. porting my product to our new machine

I just received this bug report on Debian's rsync package. I've verified it. The entry from the manpage: -C [...] Finally, any file is ignored if it is in the same directory as a .cvsignore file and matches one of the patterns listed therein. Here the patterns of a .cvsignore file is apparently used to exclude file outside the directory where the .cvsignore file is found. Any

Hi all My client want a shared folder so that only two people can access and write to it. I added the following to my smb.conf [private] writeble = yes guest ok = no path = /home/samba/private valid users = wendy, pierre write list = wendy, pierre force user = nobody All i need yo do now is make the folder "private" to nobody. How would i go on by doing that and would this work.

I'm tracking some custom OpenSSH changes (based on 4.3p2) in a local CVS repository and have run into a few problems... mainly (I believe) because of the .cvsignore files. Keep in mind the main idea here is to commit the OpenSSH source without changes, tag, then add my custom changes and add a new tag. I can probably fix these by making local modes, but I'm just wondering if there

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

On behalf of the development team of R (www.R-project.org), I would like to report the following problem with recent versions of rsync. First, some background info. The R Development Core Team uses CVS for maintainins its source code archive. Additionally, there is a mechanism for "mirroring" some important (so-called recommended) extension packages from a CRAN (Comprehensive R