Re: Enable logging remote ssh contacts
Cyrille Lefevre wrote: > > > Le 27/04/2011 20:49, Fokke Nauta a écrit : > Hi, > >> I don't have any ll in the shell. Not recognized. >> So I can't see the >> I have syslog-ng running. Should I replace that by autossh? > > syslogd must be started before sshd... does it ? > > let's try configuring both services differently : > > # backup the actual configuration > cygrunsrv -VQ syslogd > syslogd.cfg > cygrunsrv -VQ sshd > sshd.cfg > > # stop the services > cygrunsrv -E syslogd > cygrunsrv -E sshd > > # remove the services > cygrunsrv -R syslogd > cygrunsrv -R sshd > > # reconfigure the services using the .cfg parameters if different > > # -y tcpip may be added but in this case, sshd should depend on > # syslogd sshd (see the alternative below) > cygrunsrv -I syslogd -p /usr/sbin/syslogd \ > -d "CYGWIN syslog daemon" -u LocalSystem -w '' > > # since tcpip doesn't start too early, syslogd has the time > # to start before sshd does... > cygrunsrv -I sshd -p /usr/sbin/sshd -a "-D" \ > -d "CYGWIN ssh daemon" -f "8022" -u cyg_server -w \ > -y tcpip -e "CYGWIN=tty" # ntsec if XP, tty isn't necessary. > > # alternative, don't touch the syslogd service but provide it > # as an sshd depedency... > cygrunsrv -I sshd -p /usr/sbin/sshd -a "-D" \ > -d "CYGWIN ssh daemon" -f "8022" -u cyg_server -w \ > -y tcpip -y syslogd -e "CYGWIN=tty" # ntsec if XP, tty isn't necessary. > > # start the services > cygrunsrv -S syslogd > cygrunsrv -S sshd > > although, permission check (under vista at least, don't know under XP) > > somebody@somewhere /var/log > v2$ ls -ld . messages > drwxrwxrwx+ 1 somebody None 0 Mar 31 00:38 . > -rw-rw-r--+ 1 SYSTEM root 3495748 Apr 3 15:26 messages > --^ note the + here => acl > > somebody@somewhere /var/log > v2$ getfacl . messages > # file: . > # owner: somebody > # group: None > user::rwx > group::rwx > group:root:rwx > group:SYSTEM:rwx > mask:rwx > other:rwx > default:user::rwx > default:group::rwx > default:group:root:rwx > default:group:SYSTEM:rwx > default:group:Utilisateurs:r-x > default:mask:rwx > default:other:rwx > > # file: messages > # owner: SYSTEM > # group: root > user::rw- > group::rw- > group:Utilisateurs:r-x > mask:rwx > other:r-- > > at last, I prefer the VERBOSE log level than the info one : > > somebody@somewhere /var/log > v2$ grep Level /etc/sshd_config > LogLevel VERBOSE > > > Regards, > > Cyrille Lefevre > > Hi Cyrille, Thanks for your help and explanation. For a beginning: "syslogd must be started before sshd... does it ?" It does. I can read the file /var/log/messages from the Cygwin shell and it gets filled with data. Hence the reason I did not follow your instructions as I thought it was working allright. I was not able to open in from within Windows, so installed cron and copy it every 10 minutes to a different location. I am since then able to open that new file from Windows. Problem: The action of copying also creates an entry in /var/log/messages. So that file is full of these entries. What is the difference between LogLevel INFO and LogLevel VERBOSE in /etc/sshd-config? My properties of /var/log/messages (and here lies the problem that the file is not accessable from withing Windows): ls -ld messages -rw--- 1 SYSTEM root 47648 Apr 28 14:09 messages getfacl messages # file: messages # owner: SYSTEM # group: root user::rw- group::--- mask:rwx other:--- Should I use chmod on /var/log/messages? Regards, Fokke -- View this message in context: http://old.nabble.com/Enable-logging-remote-ssh-contacts-tp31478200p31495952.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Enable logging remote ssh contacts
René Berber-2 wrote: > > On 4/27/2011 1:49 PM, Fokke Nauta wrote: > >> I don't have any ll in the shell. Not recognized. > > Oops! My mistake, ll is an bash alias I defined, its just "ls -alhF > --color=tty" (actually is an alias that uses the alias ls is defined to, > but I included what both aliases do for simplicity). > >> So I can't see the >> I have syslog-ng running. Should I replace that by autossh? > > No, autossh is something else, I just kept it to show you how a Windows > service looks, like the sshd.log you have. > >> Strange enough the file /var/log/messages could not be opened by Windows. >> Tried with Textpad and Notepad. In both occasions it said: "access >> denied". >> So I installed cron and now copy /var/log/messages to a different >> location >> every 10 minutes. I can now read that file from Windows. However, copying >> that file creates an entry in the /var/log/messages file. >> So better quit syslog-ng and cron and use autossh instead? > > No, just run the following to see if everything is running as expected: > > cygrunsrv -LV > > Note the "Account" for both sshd and syslog-ng. That usually is what > gives problems. > > If both where installed using the Cygwin provided scripts, perhaps with > some help as provided in /usr/share/doc/Cygwin/.README, then > everything would work fine. My guess is that there is a difference, > which creates the problem, and it will show in the output of cygrunsrv. > If you send it to the list, we probably can spot the problem. > -- > René Berber > Hi René, Thanks. Basically, everything works fine except that it is impossible to open /var/log/messages in Windows. But, as I already answerd to Cyrille, that is perhaps a matter if using chmod to that file? Running cygrunsrv -LV generates: Service : cron Display name: Cron daemon Current State : Running Controls Accepted : Stop Command : /usr/sbin/cron -n stdin path : /dev/null stdout path : /var/log/cron.log stderr path : /var/log/cron.log Environment : CYGWIN="ntsec" Process Type: Own Process Startup : Automatic Account : .\Fokke Nauta Service : sshd Display name: CYGWIN sshd Current State : Running Controls Accepted : Stop Command : /usr/sbin/sshd -D stdin path : /dev/null stdout path : /var/log/sshd.log stderr path : /var/log/sshd.log Environment : CYGWIN="ntsec tty" Process Type: Own Process Startup : Automatic Dependencies: tcpip Account : LocalSystem Service : syslog-ng Display name: CYGWIN syslog-ng Current State : Running Controls Accepted : Stop Command : /usr/sbin/syslog-ng -F stdin path : /dev/null stdout path : /var/log/syslog-ng.log stderr path : /var/log/syslog-ng.log Process Type: Own Process Startup : Automatic Account : LocalSystem With regards, Fokke -- View this message in context: http://old.nabble.com/Enable-logging-remote-ssh-contacts-tp31478200p31496002.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Why doesn't ~/inputrc work
On 4/28/2011 12:49 AM, Harry Putnam wrote: Harry Putnam writes: I took a while to play around. One thing you may need to do is set the TERM environment variable to a proper, more capable, terminal (such as "cygwin"). Beyond that, I found that I needed to: set convert-meta on in my .inputrc and also to write the escape sequences as (for example): "\M-b": "echo meta b" Note: *one* backslash, not two! Best -- Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: untarring symlinks with ../ fails randomly
Eric Blake redhat.com> writes: ... > > > No, because they don't use ctime the way that cygwin1.dll uses ctime. > They probably have other hacks in their port of tar to work around lack > of POSIX features that cygwin1.dll is emulating. Do you mean that the implementation of ctime in cygwin1.dll might be improvable? How is it implemented? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: untarring symlinks with ../ fails randomly
On 04/28/2011 09:06 AM, Dan Grayson wrote: > Eric Blake redhat.com> writes: > ... >> >> >> No, because they don't use ctime the way that cygwin1.dll uses ctime. >> They probably have other hacks in their port of tar to work around lack >> of POSIX features that cygwin1.dll is emulating. > > Do you mean that the implementation of ctime in cygwin1.dll might be > improvable? How is it implemented? No, I'm saying that other windows ports of GNU tools most likely (mis)use ctime as birthtime, whereas cygwin properly uses ctime as ctime and exposes birthtime separately. Since the BLODA is affecting ctime, but only cygwin is exposing ctime, then only cygwin is likely to be affected by this patch. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Cygwin 1.7.8 - bash: wall: missing command
Hi all. I have a question regarding bash. The "wall" command is missing? If so, can I install it? All I get is "bash: wall: missing command". "which wall" returns nothing after searching in various directories. Thanks in advance. Regards, Jorge Ing. Jorge Peña Coordinador Técnico Programa de Energía Eólica en Uruguay Tel.: (+598) 2900-6919 ext. 3199 / 2900-9427 www.energiaeolica.gub.uy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 1.7.8 - bash: wall: missing command
On 28 April 2011 11:25, Jorge Peña wrote: > I have a question regarding bash. The "wall" command is missing? If so, can I > install it? It's in util-linux: http://cygwin.com/cgi-bin2/package-grep.cgi?grep=wall.exe Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
could not allocate memory although set with regtool
Hello, I am working with GMT and since I have to process large ammounts of data I tried to set the ammount of memory that can be used by cygwin to 1024MB using regtool. According to regtool the registry entry was created: heap_chunk_in_mb (REG_DWORD) = 0x0400 (1024) I also checked that using the registry editor and the entry was added to the cygwin folder in HKEY_LOCAL_MACHINE. Nevertheless the grdimage tool of GMT prompts an Error: GMT Fatal Error: grdimage could not allocate memory [889.89 Mb, n_items = 23328] I am using Windows 7 (32 Bit) and have 2GB RAM, so the memory should be available. Does anybody have an idea of what could be the problem? Thanks for your time and advice, Cheers, Dirk ___ WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt mit gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Using 'setup.exe' from command line / commandline ops
I am trying to use setup.exe from the command line to install a single package (bash). I found the help switch -h (Suggestion: why not have any wrong switch specification display the help?). I don't need the short cuts, and it says to use -P to specify packages It doesn't say what values are used if they aren't specified on the command line, but given the GUI behavior of using all previous values for 'defaults' *except* for the one regarding short-cuts (which seems to default to true regardless of previous selections), is it safe to assume that the command line version does the same? Assuming that was the case, I tried setup -n -P bash It then proceeded to run the GUI as though nothing had been specified on the command line. It lead me through all the normal selections (hitting Enter, to take defaults), and when I got to package selections, it selected 'ALL needing updates', instead of just 'bash'. So why didn't it just select bash for install? How do I just select a single package for install? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mkshortcut --allusers --smprograms
On 4/21/2011 10:18 AM, Jon TURNEY wrote:
> On 15/08/2010 22:12, Charles Wilson wrote:
>> On 6/29/2009 2:53 PM, Andy Koppe wrote:
>>> Shortcuts created by postinstall scripts using mkshortcut --allusers
>>> --smprograms aren't readable for ordinary users, so all they get to
>>> see in the start menu is a white dummy icon that doesn't do anything.
>>> This affects both MinTTY and rxvt, at least with Cygwin 1.7 on Windows
>>> 7. I guess the scripts could find out where the start menu is and
>>> apply the necessary rights themselves, but it would make sense and be
>>> much more convenient if mkshortcut did that.
>>
>> Andy, if you'd like to roll this change into a forward-port of your
>> other, wideAPI/locale patch, that'd be great.
>
> This issue still seems to exist, and I couldn't find an actual patch to solve
> it, so attached is an attempt at fixing this.
>
Jon, thanks for the patch. Out of curiosity, why do you do this:
ssize_t size;
size = cygwin_conv_path(CCP_WIN_W_TO_POSIX | CCP_ABSOLUTE, widepath,
NULL, 0);
if (size >= 0)
{
char *posixpath = malloc(size);
if (!cygwin_conv_path(CCP_WIN_W_TO_POSIX | CCP_ABSOLUTE, widepath,
posixpath, size))
Instead of simply using cygwin_create_path() ?
--
Chuck
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mkshortcut --allusers --smprograms
On 28/04/2011 18:03, Charles Wilson wrote:
> On 4/21/2011 10:18 AM, Jon TURNEY wrote:
>> On 15/08/2010 22:12, Charles Wilson wrote:
>>> On 6/29/2009 2:53 PM, Andy Koppe wrote:
Shortcuts created by postinstall scripts using mkshortcut --allusers
--smprograms aren't readable for ordinary users, so all they get to
see in the start menu is a white dummy icon that doesn't do anything.
This affects both MinTTY and rxvt, at least with Cygwin 1.7 on Windows
7. I guess the scripts could find out where the start menu is and
apply the necessary rights themselves, but it would make sense and be
much more convenient if mkshortcut did that.
>>>
>>> Andy, if you'd like to roll this change into a forward-port of your
>>> other, wideAPI/locale patch, that'd be great.
>>
>> This issue still seems to exist, and I couldn't find an actual patch to solve
>> it, so attached is an attempt at fixing this.
>>
>
> Jon, thanks for the patch. Out of curiosity, why do you do this:
>
> ssize_t size;
> size = cygwin_conv_path(CCP_WIN_W_TO_POSIX | CCP_ABSOLUTE, widepath,
> NULL, 0);
> if (size >= 0)
> {
>char *posixpath = malloc(size);
>if (!cygwin_conv_path(CCP_WIN_W_TO_POSIX | CCP_ABSOLUTE, widepath,
> posixpath, size))
>
> Instead of simply using cygwin_create_path() ?
Doh! I obviously didn't get that far down the page :-)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: SYSTEMROOT, cygpath, and /proc funniness
Nellis, Kenneth wrote:
In .bash_profile I use cygpath to convert several environment
variables that contain Windows paths to instead contain Unix
paths. One in particular, SYSTEMROOT, has caused several
problems, one of which is causing ClearCase's cleartool to be
non-functional. Another is strictly within Cygwin itself
where there seems to be some funny relationship between
SYSTEMROOT, having the working directory be /proc, and the
cygpath command.
The script, below, demonstrates the problem. It takes the
following options:
0: run with defaults
1: run with cd /proc
2: run with SYSTEMROOT cygpath'd
3: run with both options
-
I tried your script on my system and couldn't reproduce
the results.
I altered the script to run all cases in succession.
My results on all 4 cases (calling script with "test.sh all 3")
case=all, count=3
5572: old priority 0, new priority -19
case = 0, PWD=/tmp, SYSTEMROOT=C:\Windows,
Iter 0 @ 10:51:30: 0.07sec 0.01usr 0.00sys (19.73% cpu)
Iter 0 @ 10:51:31: 0.07sec 0.01usr 0.00sys (19.23% cpu)
Iter 0 @ 10:51:32: 0.07sec 0.01usr 0.00sys (19.23% cpu)
case = 1, PWD=/proc, SYSTEMROOT=C:\Windows,
Iter 1 @ 10:51:32: 0.08sec 0.00usr 0.03sys (37.80% cpu)
Iter 1 @ 10:51:33: 0.07sec 0.03usr 0.00sys (39.24% cpu)
Iter 1 @ 10:51:33: 0.08sec 0.00usr 0.01sys (18.75% cpu)
case = 2, PWD=/tmp, SYSTEMROOT=/Windows,
Iter 2 @ 10:51:34: 0.08sec 0.00usr 0.00sys (0.00% cpu)
Iter 2 @ 10:51:35: 0.07sec 0.00usr 0.01sys (19.23% cpu)
Iter 2 @ 10:51:35: 0.07sec 0.01usr 0.01sys (38.46% cpu)
case = 3, PWD=/proc, SYSTEMROOT=/Windows,
Iter 3 @ 10:51:36: 0.07sec 0.00usr 0.01sys (19.48% cpu)
Iter 3 @ 10:51:36: 0.07sec 0.00usr 0.03sys (41.33% cpu)
Iter 3 @ 10:51:37: 0.07sec 0.01usr 0.01sys (40.25% cpu)
Script:
#!/bin/bash
TIMEFORMAT="%2Rsec %2Uusr %2Ssys (%P%% cpu)"
case=-1
count=20
uname -a
function usage {
echo "Usage: $0 {0|1|2|3|all}"
exit 1
}
function _setup {
local case=$1
count=${2:-$count}
#echo "_setup1: case=$case, count=$count"
case $case in
0) ;;
1) cd /proc
;;
2) SYSTEMROOT=$(cygpath "$SYSTEMROOT")
;;
3) cd /proc
SYSTEMROOT=$(cygpath "$SYSTEMROOT")
;;
all)
;;
*) echo "$0: invalid parameter: $1"
usage
exit 1
;;
esac
echo "$case $count"
}
function do_test {
case=$1
use_count=$2
echo " case = $case, PWD=$PWD, SYSTEMROOT=$SYSTEMROOT, "
for ((n=1; n<=use_count; n++)); do
echo -n "Iter $1 @ $(date +'%H:%M:%S'): "
time cygpath /proc &>/dev/null
sleep 0.3
done
}
#get case & count from initial setup
read case count<<< "$(_setup "$@")"
echo "case=$case, count=$count"
# try for highest priority to minimize other procs 'stealing' cpu cycles
renice -19 $$
if [[ $case != all ]] ;then
do_test $case $count
elif [[ $case == all ]]; then
for ((case=0; case<=3; ++case)); do
# call setup before each 'do_test' to simulate original script and do
# each in a subshell to isolate any unanticipated side-effects
(
_setup $case $count &>/dev/null
do_test $case $count
)
done
fi
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Enable logging remote ssh contacts
Le 28/04/2011 14:29, Fokke Nauta a écrit : Hi, Thanks for your help and explanation. you're welcome... For a beginning: "syslogd must be started before sshd... does it ?" It does. I can read the file /var/log/messages from the Cygwin shell and it gets filled with data. right. Hence the reason I did not follow your instructions as I thought it was working allright. as you wich. What is the difference between LogLevel INFO and LogLevel VERBOSE in /etc/sshd-config? I'd like the following message which permit to identify the incoming connexion : Apr 25 23:35:03 pcvista sshd: PID 11500: Found matching DSA key: a5:44:9f:8e:2e:ea:76:7a:4f:6e:46:7f:08:25:67:6e My properties of /var/log/messages (and here lies the problem that the file is not accessable from withing Windows): ls -ld messages -rw--- 1 SYSTEM root 47648 Apr 28 14:09 messages getfacl messages # file: messages # owner: SYSTEM # group: root user::rw- group::--- mask:rwx other:--- Should I use chmod on /var/log/messages? no, setfacl %-| (getfacl messages | echo group:Users:r--) | setfacl -m -f - messages PS : replace Users by the equivalents group on your system (Utilisateurs in french under Vista, don't know under XP ?) well, the last one : v2$ id uid=1000(Cyrille) gid=513(None) groups=513(None),0(root),544(Administrateurs),545(Utilisateurs) Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bump! SSH works great, SFTP with a keypair fails. Please take a look at this log...
I've struggled with this for weeks. I'm using Cygwin v1.7.5 or v1.7.7 and see the same behavior. SSH with or without a key pair will work flawlessly every time. SFTP with a password will work fine, but SFTP with a key pair will fail every time. The server thinks the publickey is accepted and then calls the SFTP subsystem... but it will disconnect a few seconds later. sftp-server.exe has the privileged server and domain users in the NTFS security and the privilege server has modify rights. It really looks like it should be working. Any ideas? Here is the debug code from the client when attempting to SFTP with a key pair: SCHAMJI@OHCSCXXE85061MT /cygdrive/c $ sftp -v -v -v -i /cygdrive/c/id_rsa RISF01P@SDC01DERFNPA01S OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /etc/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to SDC01DERFNPA01S [10.16.107.184] port 22. debug1: Connection established. debug3: Incorrect RSA1 identifier debug3: Could not load "/cygdrive/c/id_rsa" as a RSA1 public key debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /cygdrive/c/id_rsa type 1 debug1: identity file /cygdrive/c/id_rsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4 debug1: match: OpenSSH_5.4 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.8 debug2: fd 3 setting O_NONBLOCK debug3: load_hostkeys: loading entries for host "sdc01derfnpa01s" from file "/home/SCHAMJI/.ssh/known_hosts" debug3: load_hostkeys: found key type RSA in file/home/SCHAMJI/.ssh/known_hosts:6 debug3: load_hostkeys: loaded 1 keys debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hell man-group-exchange-s roup1-sha1 debug2: kex_parse_kexinit: ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@open ssh.com,ecdsa-sha2-nistp38 v...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ecdsa-sha2-nistp256,ec dsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes 192-cbc,aes256-cbc,arc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes 192-cbc,aes256-cbc,arc debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1- 96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1- 96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-h ellman-group1-sha debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes 192-cbc,aes256-cbc,arc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes 192-cbc,aes256-cbc,arc debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1- 96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1- 96,hmac-md5-96 debug2: kex_parse_kexin
[ANNOUNCEMENT] Updated: cygutils-1.4.6-1
Cygutils is a collection of useful(?) tools for the cygwin platform. This is a bugfix release and a content update. [[ compiled using gcc-4.3.4-3 ]] CHANGES (from cygutils-1.4.4-1) * conv: no longer distribute as dos2unix, unix2dos, u2d, or d2u. Those programs now available from the separate dos2unix package. * ascii: by default, now only prints characters 0..127. Use new option --extended/-e for old behavior, printing characters 0..255. See this thread: http://cygwin.com/ml/cygwin/2010-04/msg00600.html * cygstart: Fix --reference. Allow relative paths (enables, e.g. 'cygstart calc'). Reported by Ken Hirsch. http://cygwin.com/ml/cygwin/2010-01/msg01101.html * cygdrop: Minor fixes (Christian Franke) * mkshortcut: Minor fixes (Jon TURNEY) * Updated licenses for all apps to GPLv3+ (with permission from all original contributors). TODO (call for patches): * Update lpr.cc, mkshortcut.c, readshortcut.c to use cygwin-1.7 cygwin_conv_path instead of deprecated cygwin_conv_to_win32_path. * Update (some?) utilities to handle unicode filenames, similar to IWAMURO Motonori's work on cygstart. Which utilities need this? mkshortcut and lpr, probably. Any others? -- Charles Wilson volunteer cygutils maintainer for cygwin To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
