-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Multiple vulnerabilities, ranging from integer overflows and NULL
pointer dereferences to double frees, were reported in libTIFF.
Solution: Update to =3.8.1.
More information:
http://www.gentoo.org/security/en/glsa/glsa-200605-17.xml
http://world.std.com/~jhallen/setup.hint
http://world.std.com/~jhallen/joe-3.4-1-src.tar.bz2
http://world.std.com/~jhallen/joe-3.4-1.tar.bz2
Joe
The problem was I had NetMeeting Desktop sharing running on the machine.
Stop netmeeting desktop sharing, problem went away.
:-)
...Lyall
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: [EMAIL PROTECTED] 2006-05-31 01:49:02
Modified files:
testsuite : ChangeLog
testsuite/winsup.api: cygload.h
Log message:
* winsup.api/cygload.h: Increase padding to 32768.
Patches:
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: [EMAIL PROTECTED] 2006-05-31 02:14:17
Modified files:
cygwin : ChangeLog cygtls.cc
Log message:
* cygtls.cc (_cygtls::call2): Don't call ExitThread on the main thread.
Patches:
The recent change (on 2006-05-24) to _dll_crt0() calls dll_crt0_1()
via _cygtls::call() instead of calling it directly. The call in
_cygtls::call2() to ExitThread() means that anyone using
cygwin_dll_init() will find that their main thread suddenly exits
instead of returning control to the caller
On Tue, May 30, 2006 at 02:12:22PM -0700, Max Kaehn wrote:
The recent change (on 2006-05-24) to _dll_crt0() calls dll_crt0_1()
via _cygtls::call() instead of calling it directly. The call in
_cygtls::call2() to ExitThread() means that anyone using
cygwin_dll_init() will find that their main
Original Message
From:
Sent: Monday, May 29, 2006 8:52 PM
To:
Subject: Re: Some small doc bugs in cygwin and tar packages
That's because the upstream tar package does not provide a man page. I'm
not really inclined to go creating man pages where upstream did not think
On 30 May 2006 02:26, Vilar Camara wrote:
That's right, I had looked at it and completely forgot to mention it.
But my Event Log doesn't add anyting to our discussion: there are only
log entries saying: `sshd' service started
`sshd' service stopped, exit status: 0
`sshd' service stopped,
2006/5/30, Eric Blake [EMAIL PROTECTED]:
Attached is bash_completion support for cygport. (cygwin only)
Put it into /etc/bash_completion.d/cygport
Maybe it can be added to the package, though it's only useful for cygwin.
I don't use bash_completion myself, but if someone else will verify
Hello again,
Well, things get more and more confusing. That's what I did:
- Removed c:\cygwin from PATH;
- Uninstalled cygwin services (actually only sshd);
- Installed a fresh, new cygwin instance under J:\cygwin (a NTFS
partition). Accepted default package set, only added openssh and
I use an own unattended setup of the CopSSH 1.3.10 (may 2006,
http://itefix.no/copssh), based on the Cygwin rel. 1.5.19-4 on Windows 2003
Server SP1. Hardware: Intel XEON 2.80 GHz, 2 GB RAM
Every time I restart the computer the sshd service starts but all SSH
connections are refused. In the
Has anyone done this successfuly?
Running latest cygwin.
Here is what I did:
Compiled libosip successfully:
$ locate libosip
/usr/local/lib/libosip2.a
/usr/local/lib/libosip2.dll.a
/usr/local/lib/libosip2.la
/usr/local/lib/libosipparser2.a
/usr/local/lib/libosipparser2.dll.a
On 30 May 2006 14:22, Nelson Pereira wrote:
Caveat: I haven't even /heard/ of siproxd. However:
Then the Make: This is where it fails !
resolve.c:23:26: arpa/nameser.h: No such file or directory
resolve.c:24:20: resolv.h: No such file or directory
Autoconf should have spotted this, I
Thanks Dave !
That worked !
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dave Korn
Sent: Tuesday, May 30, 2006 9:43 AM
To: cygwin@cygwin.com
Subject: RE: Trying to compile siproxd on cygwin
On 30 May 2006 14:22, Nelson Pereira wrote:
Caveat: I
... for quite some time now; here's an update to the related faq entry.
2006-05-29 Dave Korn [EMAIL PROTECTED]
* faq-api.xml (faq.api.winsock): Replace references to depracated
Win32_Winsock macro with __USE_W32_WINSOCK, and enlarge on details.
cheers,
DaveK
--
Ok, the install went good, but the Service wont start.
Windows complains about:
This application has failed to start because cygosipparser2-3.dll was
not found.
Although the file is there @
/usr/local/bin/cygosipparser2-3.dll
Regards,
Nelson Pereira
-Original Message-
From: [EMAIL
debug3: Not a RSA1 key file /home/vilarnt/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type
On Tue, 30 May 2006, Ren� Krell wrote:
I use an own unattended setup of the CopSSH 1.3.10 (may 2006,
http://itefix.no/copssh), based on the Cygwin rel. 1.5.19-4 on Windows 2003
Server SP1. Hardware: Intel XEON 2.80 GHz, 2 GB RAM
As people seem to be fond of saying nowadays, stop right here.
Nelson Pereira wrote:
Ok, the install went good, but the Service wont start.
Windows complains about:
This application has failed to start because cygosipparser2-3.dll was
not found.
Although the file is there @
/usr/local/bin/cygosipparser2-3.dll
But it is apparently not in the path
OK,
I copied the 2 DLL files to /bin and now the service starts but stops on
it's own after about 5 sec.
Regards,
NPereira
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dave Korn
Sent: Tuesday, May 30, 2006 9:43 AM
To: cygwin@cygwin.com
Subject:
On 30 May 2006 15:53, Dave Korn wrote:
2006-05-30 Dave Korn
Doh! Wrong date on the ChangeLog entry. I meant today.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
Hi,
I am new to this mailing list. If this is not the right mailing address,
please let me know what will be the mailing list.
I have old Cygwin binaries, source codes and build environment for version
1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
with Date
On 30 May 2006 17:08, Carry Suryakusuma wrote:
I have old Cygwin binaries, source codes and build environment for version
1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
with Date Execution Protection (DEP) support running on DEP enabled
processor.
Probably some
Carry Suryakusuma wrote:
I rebuilt the Cygwin1.dll using the following build environment:
1. bash version: GNU bash, version 2.03.0(2)-release (i686-pc-cygwin)
2. make version: GNU Make version 3.77, by Richard Stallman and Roland
McGrath.
3. gcc version: 2.9-cygwin-990830
4. g++ version:
Since version 3 bash has problems with path completion. For example,
here's directory listing:
shadow:~/tmp$ ls -la
total 1
drwxr-xr-x+ 4 shadow None 0 May 30 20:41 .
drwxr-xr-x+ 10 shadow root 0 May 29 20:34 ..
drwxr-xr-x+ 8 shadow None 0 Apr 26 22:16 games
drwxr-xr-x+ 5 shadow None
On 30 May 2006 17:40, burning shadow wrote:
Since version 3 bash has problems with path completion.
Since version 3, bash has had problems with readline causing spurious 'ghost'
characters to echo to the screen, particularly when scrolling through the
history buffer or using a prompt with
On Tue, May 30, 2006 at 05:24:01PM +0100, Dave Korn wrote:
On 30 May 2006 17:08, Carry Suryakusuma wrote:
I have old Cygwin binaries, source codes and build environment for version
1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
with Date Execution Protection (DEP)
Since version 3, bash has had problems with readline causing spurious 'ghost'
characters to echo to the screen, particularly when scrolling through the
history
buffer or using a prompt with non-printing chars in it. It may affect
completion too.
Is there any solution?
The real question
On 30 May 2006 18:08, burning shadow wrote:
Since version 3, bash has had problems with readline causing spurious
'ghost'
characters to echo to the screen, particularly when scrolling through the
history
buffer or using a prompt with non-printing chars in it. It may affect
completion
Vilar Camara wrote:
[snip]
The symptoms do appear like a firewall issue like Larry Hall said,
This is always a point to be rechecked. I just did it:
- All ssh.exe, ssh2.exe (Windows GUI client) and sshd.exe have full
permissions set to access and server;
- Logging on, but no log entries
Like I said, it's unlikely that this is the thing that makes the difference,
but you could
always have a quick try with the latest snapshot just in case:
http://cygwin.com/snapshots. It might also be trying the different cygwin
terminals, xterm
and rxvt as well as plain old dos console.
Brian Dessent [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I'm afraid you are probably not going to find anybody on this list
interested in even considering problems with these ancient versions. If
you can reproduce the problem you experience with a current Cygwin
snapshot then
The symptoms do appear like a firewall issue like Larry Hall said,
This is always a point to be rechecked. I just did it:
- All ssh.exe, ssh2.exe (Windows GUI client) and sshd.exe have full
permissions set to access and server;
- Logging on, but no log entries about these programs being
On 05/30/2006, Vilar Camara wrote:
After all, I'm really suspicious about that ZoneAlarm DLL. But I think I
can only purge it if I uninstall the firewall. Oh my.
You are correct. Turning it off is not enough. ZA inserts itself into the
TCP stack so turning it off is not the same as not
burning shadow wrote:
Like I said, it's unlikely that this is the thing that makes the
difference, but you could
always have a quick try with the latest snapshot just in case:
http://cygwin.com/snapshots. It might also be trying the different
cygwin terminals, xterm
and rxvt as well as
Vilar Camara wrote:
[snip]
Now that's strange: in that verbose list there is no program listening
on port 22. The only reference to sshd is in the following block:
UDP127.0.0.1:2186 *:*2848
C:\WINDOWS\system32\ZoneLabs\vetredir.dll
Korn, Hall and Berber,
I'd really like to thank you for all your support tracing my problem. I've
uninstalled ZoneAlarm and everything works fine now.
Complete product description follows: ZoneAlarm Security Suite, version
6.1.744.001. Last year I was using an older version and had no
On Tue, May 30, 2006 at 09:18:56PM -0500, Yaakov S (Cygwin Ports) wrote:
While attempting to package eric3, python (2.4.3-1) just segfaults on
the included install.py script before it can do anything else. This
used to work with cygwin-1.5.18-1 and python-2.4.1-1, and since I've
had similar
I'd really like to thank you for all your support tracing my problem. I've
uninstalled ZoneAlarm and everything works fine now.
Just an additional information: I've installed ZoneAlarm Free Edition and
sshd is working. My previouos complaints were about ZoneAlarm Pro. So, it's
something
Vilar Camara wrote:
I'd really like to thank you for all your support tracing my problem.
I've uninstalled ZoneAlarm and everything works fine now.
Just an additional information: I've installed ZoneAlarm Free Edition
and sshd is working. My previouos complaints were about ZoneAlarm Pro.
So,
From: Vilar Camara
I'd really like to thank you for all your support tracing my
problem.
I've uninstalled ZoneAlarm and everything works fine now.
Just an additional information: I've installed ZoneAlarm Free
Edition and sshd is working. My previouos complaints were
about ZoneAlarm
On 5/30/06, Dave Korn wrote:
... for quite some time now; here's an update to the related faq entry.
Thanks, it's great to get patches like this. It's updated now:
http://cygwin.com/faq/faq.api.html#faq.api.winsock
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
Gary R. Van Sickle wrote:
1. Does ZoneAlarm cause the same volume of havok with other software
as it does with Cygwin? The equation appears to be Cygwin +
ZoneAlarm = Disaster, but I have a hard time believing that it isn't
really a system of equations more along the lines of
On Tue, May 30, 2006 at 10:40:14PM -0500, Gary R. Van Sickle wrote:
2. Would it make any sense to have cygcheck look for ZoneAlarm, any
and all AV programs, Google Desktop, etc etc etc, and at least
prominently flag their existence, if not make some clear statement to
the effect of This program
Cygwin:
I put the 200 GB drive into an XP box and ran Cygwin df -- same result.
Cygwin utilities, including df, work fine a 250 GB drive in the same XP
box.
I must assume that the 200 GB disk is corrupted, or is failing.
David
--
Unsubscribe info:
46 matches
Mail list logo
