Displaying 20 results from an estimated 300 matches similar to: "[Bug 1043] Trusted IRIX Support"
2005 May 12
0
[PATCH] Trusted IRIX Support
I developed a better prototype quicker than I expected.
Please provide feedback. It's been a few years since I've used autoconf,
so I'm not certain the new defines were integrated correctly.
Jason
diff -r -C3 openssh-4.0p1/acconfig.h openssh-4.0p1.trix/acconfig.h
*** openssh-4.0p1/acconfig.h Fri Feb 25 17:07:38 2005
--- openssh-4.0p1.trix/acconfig.h Thu May 12 10:32:25
2003 Aug 22
14
[Bug 252] Patch for use of /etc/default/login
http://bugzilla.mindrot.org/show_bug.cgi?id=252
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #212 is|0 |1
obsolete| |
------- Additional Comments From dtucker at zip.com.au 2003-08-22 14:14 -------
2003 Sep 29
1
Bus Error with OpenSSH 3.7.1p2 on Solaris 8, SPARC 64-bit, YASSP
I had a problem much like the one that Matthias Koeppe
experienced. I would only get the BUS error when
running in a YASSP-modified system, though. The
binary worked fine on a non-YASSP host.
I applied his change to use a long for the mask, and
it works now.
Cheers,
-Thomas
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
2003 Oct 07
2
Fwd: Re: Bus Error with OpenSSH 3.7.1p2 on Solaris 8, SPARC 64-bit, YASSP
The following patch appears to fix the BUS error
received on Solaris 8. This problem manifests as an
immediate disconnect with no apparent cause
immediately after authentication with the host.
--- Darren Tucker <dtucker at zip.com.au> wrote:
> Date: Tue, 30 Sep 2003 09:35:26 +1000
> From: Darren Tucker <dtucker at zip.com.au>
> Subject: Re: Bus Error with OpenSSH 3.7.1p2 on
2004 Jan 07
1
openssh 3.7.1p2 fault on solaris 9 for sparc when built as 64-bit
I built OpenSSH as a 64-bit binary on Solaris 9, using gcc 3.3.2,
OpenSSL 0.9.7c and zlib 1.2.1. sshd starts up normally, and will begin
the login session, however, some time after it reads /etc/default/login,
it faults and kills the connection. There are no error messages logged
to syslog (with LogLevel set to DEBUG) or with the -ddd option.
Here's a truss of the failure:
8132:
2003 Oct 21
2
Fwd: Re: Bus Error with OpenSSH 3.7.1p2 on Solaris 8, SPARC 64-bit
The story of this problem, AFAIK, is that Solaris 8 YASSP and JASS and vigilant/paranoid sysadmins have been known to set a restricitve umask in /etc/default/login. OpenSSH compatibility for Solaris 8 has been spotty at times for sparcv9 targets. This time, when a sparcv9 binary tries to sscanf(3C) the numeric umask as a long octal and put it in a mode_t, SIGBUS happens.
What this looks like in
2012 Jun 26
0
CESA-2012:1043 Important CentOS 5 libwpd Update
CentOS Errata and Security Advisory 2012:1043 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1043.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
1f840991f4ec80bfcbd90c844d598645eb115624d383e7eb1cc76b1b8ecc396a libwpd-0.8.7-3.1.el5_8.i386.rpm
2016 May 13
0
CEBA-2016:1043 CentOS 7 slapi-nis BugFix Update
CentOS Errata and Bugfix Advisory 2016:1043
Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1043.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
f2156536305cd35293215ae090b1b5864396a51a764d17613de04752c567a9ee slapi-nis-0.54-9.el7_2.x86_64.rpm
Source:
2016 Feb 16
0
[Bug 1043] Linux 4.3.1: "iptables: Protocol wrong type for socket"
https://bugzilla.netfilter.org/show_bug.cgi?id=1043
Pablo Neira Ayuso <pablo at netfilter.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |pablo at netfilter.org
--- Comment #1 from Pablo
2016 Feb 16
0
[Bug 1043] Linux 4.3.1: "iptables: Protocol wrong type for socket"
https://bugzilla.netfilter.org/show_bug.cgi?id=1043
Daniel Fraga <fragabr at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Daniel Fraga <fragabr at
2015 May 06
0
[Bug 1043] Trusted IRIX Support
https://bugzilla.mindrot.org/show_bug.cgi?id=1043
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |LATER
--- Comment #5 from Darren Tucker <dtucker at
2016 Aug 02
0
[Bug 1043] Trusted IRIX Support
https://bugzilla.mindrot.org/show_bug.cgi?id=1043
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #6 from Damien Miller <djm at mindrot.org> ---
Close all resolved bugs after 7.3p1 release
2007 May 31
0
[1043] trunk/wxruby2/samples/bigdemo: Don''t manually call destroy
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2001 Aug 07
1
R 1.3.0 bug: after "y _ 10; x[[1]] _ y", assigning to "y[1]" modifies "x" (PR#1043)
After a list element has been assigned from a vector variable,
assigments to elements of the original vector variable modify the copy
stored in the list as well.
Here's a transcript illustrating the problem:
R : Copyright 2001, The R Development Core Team
Version 1.3.0 (2001-06-22)
[ . . . ]
> x _ list()
> y _ 10
> x[[1]] _ y
2003 Sep 25
1
Bus Error with openssh 3.7.1p1 on 64-bit Sparc/Solaris
I compiled openssh 3.7.1p1 on Solaris 9 with the Forte compiler in
64-bit mode. After authentication, a forked child of sshd dies with a
Bus Error in `read_etc_default_login' (session.c).
The reason is the use of `sscanf' with control string "%5lo" on a
`mode_t' value. On Solaris in 64-bit mode, `mode_t' is an `unsigned
int' (32 bits), whereas `long' is 64
2014 Aug 14
0
Problem with enabling /etc/default(s)/login on Cygwin
Hi,
below is a patch which simply removes a Cygwin-specific piece of code
from OpenSSH. Input from a system admin educated me how useful this
option could be on Cygwin as well. However, way back when the call to
read_etc_default_login got disabled on Cygwin hardcoded in session.c,
rather than just setting --disable-etc-default-login when building the
Cygwin version of OpenSSH. So, here's
2003 Sep 16
2
openssh 3.7p1 bus error on sparcv9
openssh 3.7p1 sshd on Solaris 8 / sparcv9:
sshd runs fine, and starts to allow the login. However, when reading
from /etc/default/login, I get a bus error. I am able to get sshd to
work by commenting out these lines in session.c:
1015,1018c1015
< # ifdef HAVE_ETC_DEFAULT_LOGIN
< read_etc_default_login(&env, &envsize, pw->pw_uid);
< path =
2015 Mar 13
0
[PATCH] sd, mmc, virtio_blk, string_helpers: fix block size units
On 6 March 2015 at 03:47, James Bottomley
<James.Bottomley at hansenpartnership.com> wrote:
> From: James Bottomley <JBottomley at Parallels.com>
>
> The current string_get_size() overflows when the device size goes over
> 2^64 bytes because the string helper routine computes the suffix from
> the size in bytes. However, the entirety of Linux thinks in terms of
>
2015 Mar 13
0
[PATCH] sd, mmc, virtio_blk, string_helpers: fix block size units
On 6 March 2015 at 03:47, James Bottomley
<James.Bottomley at hansenpartnership.com> wrote:
> From: James Bottomley <JBottomley at Parallels.com>
>
> The current string_get_size() overflows when the device size goes over
> 2^64 bytes because the string helper routine computes the suffix from
> the size in bytes. However, the entirety of Linux thinks in terms of
>
2018 Aug 31
0
[PATCH] PCI: add prefetch quirk to work around Asus/Nvidia suspend issues
[+cc Intel folks]
On Fri, Aug 31, 2018 at 03:30:57PM +0800, Daniel Drake wrote:
> On over 40 Intel-based Asus products, the nvidia GPU becomes unusable
> after S3 suspend/resume. The affected products include multiple
> generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs
> many errors such as:
>
> fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR]