After connecting through ssh immediately my connection is getting
closed.
C:\WINDOWS>ssh -vvv 10.72.248.117 -l cyg_server OpenSSH_5.7p1, OpenSSL
0.9.8q 2 Dec 2010
debug2: ssh_connect: needpriv 0
debug1: Connecting to 10.72.248.117 [10.72.248.117] port 22.
debug1: Connection established.
debug1: p
After connecting through ssh immediately my connection is getting
closed.
C:\WINDOWS>ssh -vvv 10.72.248.117 -l cyg_server
OpenSSH_5.7p1, OpenSSL 0.9.8q 2 Dec 2010
debug2: ssh_connect: needpriv 0
debug1: Connecting to 10.72.248.117 [10.72.248.117] port 22.
debug1: Connection established.
debug1: p
On 2/8/2011 9:14 PM, Gerry Reno wrote:
Something else I just discovered after upgrading to 1.7.7 is that I now
have lost the ability to login via ssh.
I have OpenSSH installed and running sshd as a service. Both password
and keys accepted. But now neither means will work.
# ssh -i keypai
Something else I just discovered after upgrading to 1.7.7 is that I now
have lost the ability to login via ssh.
I have OpenSSH installed and running sshd as a service. Both password
and keys accepted. But now neither means will work.
# ssh -i keypair1.pem Administrator@MACHINE_IP
Last
On 02/08/2011 12:15 PM, Kimbo Mundy wrote:
>> I have not seen that issue, and you're the first to report it, but I'll
>> see if I can reproduce it.
I was able to reproduce this, but not on my machine (thanks Corinna for
getting me set up); and the odd thing was that the problem disappears
when com
On 2/8/2011 3:32 PM, Cyrille Lefevre wrote:
Le 08/02/2011 22:42, Hans Horn a écrit :
Trying some of the more recent revisions listed on the "Cygwin Time
Machine".
e.g. ftp://www.fruitbat.org/pub/cygwin/circa/2011/01/11/194023
All give me "Unable to get ...setup.bz2.sig" and
then "Unable to get
Le 08/02/2011 22:42, Hans Horn a écrit :
Trying some of the more recent revisions listed on the "Cygwin Time
Machine".
e.g. ftp://www.fruitbat.org/pub/cygwin/circa/2011/01/11/194023
All give me "Unable to get ...setup.bz2.sig" and
then "Unable to get ...setup.ini.sig".
What gives?
does setup
On 2/8/2011 5:25 PM, Paul Maier wrote:
The best thing to do is to skip any flags for 'ls'. If cygwin has to open
the file to fill in a particular piece of data, you're going to see
significant delays on a slow file-system/driver.
So the difference is, that "ls -l" openes all files, reading in
On 2/8/2011 4:42 PM, Hans Horn wrote:
On 2/8/2011 1:06 PM, Corinna Vinschen wrote:
On Feb 8 16:02, Larry Hall (Cygwin) wrote:
On 2/8/2011 3:54 PM, Hans Horn wrote:
Corinna,
Last week I updated openssh to 5.7p1-1, just to realize that I cannot connect
anymore. Reverting to 5.6p1-2 solved the i
> The best thing to do is to skip any flags for 'ls'. If
> cygwin has to open
> the file to fill in a particular piece of data, you're going
> to see significant
> delays on a slow file-system/driver.
So the difference is, that "ls -l" openes all files, reading in all bytes to
count them;
whil
On 2/8/2011 1:06 PM, Corinna Vinschen wrote:
On Feb 8 16:02, Larry Hall (Cygwin) wrote:
On 2/8/2011 3:54 PM, Hans Horn wrote:
Corinna,
Last week I updated openssh to 5.7p1-1, just to realize that I cannot connect
anymore. Reverting to 5.6p1-2 solved the issue.
Saturday I updated to 5.8p1-1 f
Hi!
> Sure but you have a mobile phone in the mix here, right?
> You're relying
> on some software to talk to the phone. That's the driver.
> So that's one
> possibility. And the one that seemed most likely to me if
> it's affecting
> performance even when you're not accessing the drive wit
On 02/08/2011 03:28 PM, Gerry Reno wrote:
> On 02/08/2011 03:14 PM, Larry Hall (Cygwin) wrote:
>
>> On 2/8/2011 2:47 PM, Gerry Reno wrote:
>>
>>
>>
>>
>>> As you can see it is not just the lapack0.sh file in /etc/profile.d/.
>>> Even when I remove lapack0.sh the problem just moves to anoth
On Feb 8 16:02, Larry Hall (Cygwin) wrote:
> On 2/8/2011 3:54 PM, Hans Horn wrote:
> >Corinna,
> >
> >Last week I updated openssh to 5.7p1-1, just to realize that I cannot connect
> >anymore. Reverting to 5.6p1-2 solved the issue.
> >
> >Saturday I updated to 5.8p1-1 finding the same failure to co
I've updated the version of OpenSSL to 0.9.8r-1. This also includes the
openssl-devel packages.
This is an upstream security release fixing CVE-2011-0014. There's no
official release message, but here's a pointer to the security advisory:
http://www.openssl.org/news/secadv_20110208.txt
The Cygw
On 2/8/2011 3:54 PM, Hans Horn wrote:
Corinna,
Last week I updated openssh to 5.7p1-1, just to realize that I cannot connect
anymore. Reverting to 5.6p1-2 solved the issue.
Saturday I updated to 5.8p1-1 finding the same failure to connect as with
5.7p1-1. Unfortunately 5.6p1-2 is not among the
Corinna,
Last week I updated openssh to 5.7p1-1, just to realize that I cannot
connect anymore. Reverting to 5.6p1-2 solved the issue.
Saturday I updated to 5.8p1-1 finding the same failure to connect as
with 5.7p1-1.
Unfortunately 5.6p1-2 is not among the setup choices anymore.
How can I g
On 02/08/2011 03:14 PM, Larry Hall (Cygwin) wrote:
> On 2/8/2011 2:47 PM, Gerry Reno wrote:
>
>
>
>> As you can see it is not just the lapack0.sh file in /etc/profile.d/.
>> Even when I remove lapack0.sh the problem just moves to another file.
>>
>> And the problem is not consistent except when I
On 2/8/2011 2:47 PM, Gerry Reno wrote:
As you can see it is not just the lapack0.sh file in /etc/profile.d/.
Even when I remove lapack0.sh the problem just moves to another file.
And the problem is not consistent except when I try to run bash as a
login shell and there it occurs without fail
On Wed, 02 Feb 2011 12:47:00 -0700, Eric Blake wrote:
> On 02/02/2011 09:38 AM, Philipp Wiendl wrote:
> > Hello,
> >
> > today i installed cygwin v1.7 with the new v4 bash package.
> > I tried to run ssh-host-config and got following error:
> >
> > $ ssh-host-config -y
> > *** Query: Overwrite exis
On Wed, Feb 09, 2011 at 12:06:07AM +0900, wynfi...@gmail.com wrote:
>I want to write a small assembly language routine to do some heavy bit
>slogging and interface it to a C language program.
>
>Does anybody have any templates to show how this should be done.
>
>Stack control & variable definitions
When running rebaseall, I receive a #13 error from FixImage:
$ /bin/rebaseall
/usr/lib/cygicudata.dll: skipped because nonexistent
/usr/lib/cygicui18n.dll: skipped because nonexistent
/usr/lib/cygicuio.dll: skipped because nonexistent
/usr/lib/cygicule.dll: skipped because nonexistent
/usr/lib/cyg
I want to write a small assembly language routine to do some heavy bit slogging
and
interface it to a C language program.
Does anybody have any templates to show how this should be done.
Stack control & variable definitions for linking.
Thanks
--
Problem reports: http://cygwin.com/prob
> Has anyone written anything into their bash profile or whatever that goes
> through each windows environment variable currently extant, and resets them
> via CYGPATH
>
> e.g.
>
> Before, @ start of .bashrc
> ETC=C:\WINDOWS\ETC
>
> After run of .bashrc
> ETC=`$(cygpath -u '$ETC')`; EXPORT ETC
On Tue, Feb 8, 2011 at 1:50 PM, JonY wrote:
>
> Csaba:
> After double checking, I see mingw64-x86_64-binutils as a requirement of
> mingw64-x86_64-gcc-core. This should install binutils when you install
> mingw-w64 gcc. Can you confirm that its not installed at all?
>
Whoops, my bad. I selected m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/8/2011 19:15, JonY wrote:
> On 2/8/2011 19:14, Csaba Raduly wrote:
>> On Tue, Feb 8, 2011 at 2:51 AM, JonY wrote:
>>>
>>> How did you install mingw64-x86_64? I am puzzled how this can happen,
>>> looks like binutils wasn't installed properly.
>
On Feb 8 13:14, marco atzeri wrote:
> On Tue, Feb 8, 2011 at 12:59 PM, Corinna Vinschen wrote:
> > On Feb 7 22:38, marco atzeri wrote:
> >> Suggestion for debugging ?
> >
> > Build the Cygwin DLL for debugging (just -g, no -O2), build octave for
> > debugging, and try to find the problem.
> >
>
On Tue, Feb 8, 2011 at 12:59 PM, Corinna Vinschen wrote:
> On Feb 7 22:38, marco atzeri wrote:
>> I am testing latest release candidate for octave, and only on cygwin using
>> the fltk graphics interface when we try to print through ghostscript we have:
>>
>> octave 4236 E:\cygwin2\bin\octave-3.3
On Feb 7 22:38, marco atzeri wrote:
> I am testing latest release candidate for octave, and only on cygwin using
> the fltk graphics interface when we try to print through ghostscript we have:
>
> octave 4236 E:\cygwin2\bin\octave-3.3.92.exe: *** fatal error -
> Internal error: TP_NUM_C_BUFS too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/8/2011 19:14, Csaba Raduly wrote:
> On Tue, Feb 8, 2011 at 2:51 AM, JonY wrote:
>>
>> How did you install mingw64-x86_64? I am puzzled how this can happen,
>> looks like binutils wasn't installed properly.
>
> mingw64-x86_64-binutils is a separa
On Tue, Feb 8, 2011 at 2:51 AM, JonY wrote:
>
> How did you install mingw64-x86_64? I am puzzled how this can happen,
> looks like binutils wasn't installed properly.
mingw64-x86_64-binutils is a separate package which also has to be
selected for installation. mingw64-x86_64-gcc has no dependency
On 2/7/11 5:51 PM, JonY wrote:
> How did you install mingw64-x86_64? I am puzzled how this can happen,
> looks like binutils wasn't installed properly.
I installed it via setup.exe.
>
> Try adding -v for verbose output.
>
>
>
$ x86_64-w64-mingw32-g++ -v helloworld.cpp
Using built-in specs.
C
32 matches
Mail list logo
