OpenSSH 2.9 problems
I have some problems with the newly updated OpenSSH 2.9. 1. Sshd fails to authenticate via PAM. May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied 2. ln -s hostname `which ssh`; ./hostname doesn't work anymore. It used to slogin to the host in the previous versions but now it just shows the help screen. 3. Somehow the default location of the ssh host key files has been changed from /etc/ssh to /etc. Was it intentional? Any ideas? -- / /__ __Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp Freeze this moment a little bit longer, make each impression a little bit stronger.. Experience slips away -- Time stand still To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: isdn stops working when load increases
Alexander et al,
# Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this?
# Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn:
#
# I think Hellmuth choosed a good value for rtprio, and I didn't think it
# solves your problem if you increase the value, but feel free to play a
*De*creasing gives it higher priority, according to rtprio(1).
# little bit with it (I think isdnd slowes down because of a lot of
# interrupts, and if I didn't have a wrong understanding of the system,
# rtprio didn't helps in this case).
#
# echo 'removing previous isp0 config'
# ifconfig isp0 delete -link1 down
# echo 'setting sppp options'
# ispppcontrol isp0 myauthproto=pap myauthname= myauthsecret=
hisauthproto=none callin
# echo 'configuring isp0'
# ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0x link1 2/dev/null
#
# What's your defaultroute? I use -interface isp1.
5.6.7.8 (modified for the purpose of this mail :-)
# BTW: I use /etc/start_if.isp1 to configure the interface, no need to
# modify rc.isdn, e.g.:
# ---snip---
# (11) root@ttyp0 # less /etc/start_if.isp1
# ifconfig isp1 link1 0.0.0.0 0.0.0.1 netmask 255.255.0.0
# ispppcontrol isp1 $(cat /etc/isdn/connect-CBC.parameters) enable-vj
# ifconfig isp1 down
# ---snip---.
Ah, so that's how it's done properly.
# While we're at it, maybe someone wants to commit something like this:
# ---snip---
# --- /usr/src/etc/rc.isdnSat Apr 28 14:49:22 2001
# +++ /etc/rc.isdnSun Apr 29 15:37:04 2001
# @@ -38,6 +38,23 @@
# [Yy][Ee][Ss])
# echo -n 'ISDN subsystem setup:'
#
# + # Terminal type for fullscreen mode, default to syscons driver
# + #
# + if [ ! -n ${isdn_ttype} ]; then
# + isdn_ttype=cons25
# + fi
# + if [ -n ${isdn_screenflags} ]; then
# + /usr/sbin/vidcontrol ${isdn_fsdev} ${isdn_fsdev} 21
${isdn_screenflags}
# + fi
...
# ---snip---
# (I think the isdn_ttype part isn't needed anymore, someone committed
# something like this already, but the screenflags part is useful for me)
Yup, that was me :-)
Can you provide a patch against -current and also a patch adding
isdn_screenflags to /etc/defaults/rc.conf and rc.conf(5)? It's important
to document all the knobs there. Should be easy.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP! bad bug in -current.
On Wed, May 02, 2001, Robert Watson wrote: On Tue, 1 May 2001, Jordan Hubbard wrote: Say, FreeBSD is usually pretty safe, even in CURRENT. Has something near this magnitude of Really Bad Stuffage snuck into the codebase before? No, it's not common, and it generally takes a Dane swinging something sharp to inflict quite this much damage on our user base. ;-) Obviously I haven't been playing in the right bits of the system, I'll have to start hacking the low-level stuff in FFS some more... I tend not to cause permanent damage to file systems, sadly. I think we can all take lessons from phk here -- he achieves a level of destructiveness that makes even the pro's marvel in wonder. *grin* Its ok. phk has just reminded us of what -current really is .. :-) Adrian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Rfork'd threads, signals, and LDTs
On Sat, 5 May 2001, Andrew Gallatin wrote: Daniel Eischen writes: OK, thanks. Here's my guess at what should be changed for the Linux emulator. If this looks correct, I'll commit it. Hmm, I wonder how linuxthreads works under FreeBSD without this change... This breaks at least one version of the IBM JDK that I have laying around.. If anything, we may have two errors (at least partially) canceling each other out. I think it needs more work/thought prior to committing. We're still OK with the change to FreeBSDs native signal trampoline though, right? I'll hold off on the Linux emulator changes until we can figure out what the problem is. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: OpenSSH 2.9 problems
In article [EMAIL PROTECTED], Akinori MUSHA [EMAIL PROTECTED] wrote: I have some problems with the newly updated OpenSSH 2.9. 1. Sshd fails to authenticate via PAM. May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied I am seeing this same problem. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: OpenSSH 2.9 problems
In article [EMAIL PROTECTED], John Polstra [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Akinori MUSHA [EMAIL PROTECTED] wrote: I have some problems with the newly updated OpenSSH 2.9. 1. Sshd fails to authenticate via PAM. May 5 19:18:07 archon sshd[803]: fatal: PAM setcred failed[6]: Permission denied I am seeing this same problem. Here's another one: blake$ slogin localhost socket: Protocol not supported === Eh? jdp@localhost's password: John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in fxp driver
Jonathan Lemon writes: Please consider the case where there are two mbuf chains being transmitted, which look like this: Um. Not Possible. I thought m_copypacket() of a cluster mbuf would yield exactly this situation (two headers pointing to the same data region). -Arcihe __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic in fxp driver
On Sat, May 05, 2001 at 04:04:27PM -0700, Archie Cobbs wrote: Jonathan Lemon writes: Please consider the case where there are two mbuf chains being transmitted, which look like this: Um. Not Possible. I thought m_copypacket() of a cluster mbuf would yield exactly this situation (two headers pointing to the same data region). Well, only external mbufs can be shared, not mbuf chains; and clusters are accessed through the (unused) mbuf that comprises the chain. I believe Terry may have been referring to some local modifications that is in his code, which permits the scenario he describes. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Rfork'd threads, signals, and LDTs
Daniel Eischen writes: We're still OK with the change to FreeBSDs native signal trampoline though, right? I'll hold off on the Linux emulator changes until we can figure out what the problem is. Yes, I was just commenting on the linulator patch you posted. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
OpenSSL 0.9.6a for testing
Hi all, Please test binary compatibility of the OpenSSL 0.9.6a release available from the below address. By this, I mean: test whether your SSL applications such as webservers, etc, continue to work without a recompile after making world. Since 0.9.6a is a point release along the 0.9.6-STABLE branch, I expect compatibility to be maintained for all users. I'd like to import this into -current later this week. http://www.freebsd.org/~kris/openssl-0.9.6a.tar.bz2 http://www.freebsd.org/~kris/openssl-0.9.6a.diff (Untar the .tar.bz2 file, and apply the patch, and it should build fine). Kris PGP signature
Re: cp -u patch
Jeroen Ruigrok/Asmodai [EMAIL PROTECTED] writes: Question is, do we want to add this to our cp? I found it handy for stuff like: please, what is the difference between this : cp -Ruv mozilla mozilla-test and that : cd mozzila; find . | cpio -pdm ../mozzila-test ? thanks. so that my mozilla CVS tree [not touched] only overwrites the mozilla-test files which are older. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
