similar to: [PATCH] contrib/cygwin/ssh-host-config: Fix a CRLF/LF issue

Hi, could somebody with checkin rights please apply the below patch? It would be helpful to have this in 5.9p1. I revamped the Cygwin-specific service installer script ssh-host-config. The actual functionality is the same, the revisited version is just more exact when it comes to check for problems which disallow to run certain aspects of the script. So, part of this script and the also

Hi, below is a patch to contrib/cygwin/ssh-host-config and the corresponding README in the same dir. It adds a `--port' option to the config script to allow setting another port than 22 for sshd. Additionally the script used to add `sshd 22/tcp' to the services file while the IANA proposes `ssh 22/tcp' and `ssh 22/udp' as services entries. The new version removes old `sshd'

Hi, I have attached two new shell scripts `ssh-host-config' and `ssh-user-config' which will replace the script `ssh-config' in the next Cygwin OpenSSH release. Could somebody with write access please remove contrib/cygwin/ssh-config from the OpenSSH repository and add these two attached files instead? The third attached file is the diff for contrib/cygwin/README. Thanks in

Hi, the below patch to contrib/cygwin is a major rework to allow various changes in the installation process on Cygwin machines. The important changes are: - New Makefile, providing a `cygwin-postinstall' target which allows to create a base installation as in the Cygwin distribution, which should be run right after a `make install'. - Additional information given in the README

Hi, the below patch is necessary for the contrib/cygwin/ssh-host-config script to work on Cygwin 1.5.x as well as on the new Cygwin 1.7.x. The information given for the setting of the CYGWIN environment variable is wrong for both releases so I just removed it, together with the unnecessary (Cygwin 1.5.x) or wrong (Cygwin 1.7.x) default setting. Could somebody with checkin rights please apply

Hi, would you mind to apply the below patch? It fixes Cygwin's ssh-host-config script in various ways: - Remove old code to remove the "sshd/22" entry from /etc/services. This code fixes a problem which only existed in installations which are more than 10 years old. - Handle the StrictMode setting interactively. - Fix regular expressions looking for white spaces. - Make the

Hi, the following patch patches the files in contrib/cygwin. The changes are necessary to allow a better support of privilege separation. On NT machines the script asks now if it should create a user called "sshd" and all that. Additionally it creates the /etc/ssh_config and /etc/sshd_config files follows the latest versions. Would you mind to apply this to the official OpenSSH

Hi, We will probably do an openssh-5.5p1 release soon, mainly for the sshd_config:AuthorizedKeysFile bug, but containing a few other small patches too. If you have any portability fixes that need to go in then

Hi, the below patch makes the query for the localized name of the local administrators group more reliable. Can somebody check it in, please? Thanks, Corinna Index: ssh-host-config =================================================================== RCS file: /cvs/openssh_cvs/contrib/cygwin/ssh-host-config,v retrieving revision 1.15 diff -p -u -r1.15 ssh-host-config --- ssh-host-config 21 Sep

Hi, the attached patch changes the ssh-host-config script in the following way: - Actually exit if ssh processes are still running. The "exit 1" is commented out for testing purposes and I accidentally left it this way when sending the patch to this list :-( - Create the Windows NT account "sshd" so that it's deactivated. So even if the administrator(s) for some

No, I don't. But I do know that Samba provides transparent file access -- it has no idea what data is in the files it offers to the clients. It could be a database, a JPEG, a text document, or an executable program. What you suggest would be an extremely bad idea. You need better clients -- it is the clients that interpret the contents of the file. Samba is just another file access method.

On 25/07/2020 4:48 p.m., nospam at altfeld-im.de wrote: > Dear R developers, > > I am developing an R package which returns strings with new line codes. > I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows platforms. > > What is the recommended best practice for package developers (and code in base R) for coding new lines in

Hi everybody! I hope that you are not already "pissed off" of all the crlf/lf conversion discussion between dos and unix ;-) Concerning that topic I have a question / suggestion: This is what we have: We are using a Win NT 4.0 Server with Win95 clients. Additionally we have a Sun (Solaris 2.5) running in the same network. To access the Sun in character mode we use a terminal

Hi. I've made a strange observation. When having Dovecot (at least) with maildir and moving (via IMAP) mail received by some client (Evolution 3.4) into it the following happens: Regardless of whether the mail was originally(!) set with CRLF or LF (i.e. when I use netcat to submit the plain SMTP to the relaying MTA). When the client (Evolution) had received the mail via POP3 before moving

Dear R developers, I am developing an R package which returns strings with new line codes. I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows platforms. What is the recommended best practice for package developers (and code in base R) for coding new lines in strings? And just out of curiosity: What is the reason (or history) for preferring

The cygwin 'cygpath' command can now convert arbitrary windows and unix paths into the short ms-dos 8.3 equivalents. This tools might allow the windows build system to better deal with those messy long Windows file and directory names that contain spaces. EG: warneg@GRDGROL99X1028: src [1]$ pwd /cygdrive/c/Documents and Settings/WarnesGR/My Documents/cygwin_home/src/gregmisc/src

../libtool: line 1231: cygpath: command not found You need to put cygpath in your PATH. This might also be why configure is failing. Best, Tristan --20cf307f35267e30eb0505f59648 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi,<br><div class=3D"gmail_extra"><br><div class=3D"gmail_=

I'm forced to use Windows at work, so I make very heavy use of Cygwin (http://cygwin.com/), a very wonderful thing. One way I use it is with this handy little shell script&#058; Code: #!/bin/sh MSO="/cygdrive/c/Program Files/Microsoft Office/OFFICE11" if [ -n "$1" ]; then "$MSO"/WORDVIEW.EXE "$(cygpath -w "$@")" & else

below is a very simple bash script to run Sweave from a cygwin terminal, run pdflatex on the generated .tex file, and then view the resulting .pdf output. i usually use cygwin when i am (forced to be on) Windoze, but i found a few issues with paths that this script works around. pdfview, used in the script, is simply:

Hi, could somebody apply the below patch, please? It removes a couple of environment variables which are propagated to the child process so far, but which not really necessary to keep child processes running. What's left now is the bare minimum which is requested by scripts, typically. Thanks, Corinna Index: openbsd-compat/bsd-cygwin_util.c