Problem: FreeBSD 7.x ssh v2 nss_ldap
I see a problem on two systems running FreeBSD 7.0 or 7.1 which are configured as OpenLDAP clients using the nss_ldap module. When someone logs on using ssh protocol version 2 the session will not be initialized correctly. The user will only get his primary group affiliation but no affiliation to other groups (memberUid attribute in LDAP group entries). On 7.1 the ssh login process hangs forever with open ldap queries, on 7.0 the group list is incomplete. On several 6.x systems, all works correctly. I have used the configuration for years now. There are some workarounds I found: a) use ssh protocol version 1 b) set UseLogin to yes in sshd_config c) avoid ssl encryption in communication to ldap server (ldap://... uri instead of ldaps://... in ldap.conf) Does anybody see similar problems? Does anybody have an idea what may couse the problem? Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Patch for MS Hyper V (virtualization)
On Tuesday 14 April 2009 8:46:51 pm Sergey Babkin wrote: John Baldwin wrote: Your printf() probably isn't in the right place. pci_add_map() uses PCIB_READ_CONFIG() directly and doesn't use pci_read_config(), so if your printf is in pci_read_config_method() in pci.c it won't see them. Try hooking the cfg operations in sys/amd64/pci/pci_cfgreg.c instead. The printf was in pci_write_config(). Yes, that won't catch the PCIB_WRITE_CONFIG()'s in pci_add_map(). -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
ac97 interface q
ac97_if.m defines 'read' method to return int and 'write' method to take u_int32_t data and return int. Calls to AC97_READ and AC97_WRITE are present only in ac97.c and from those calls it is evident that the calling code expects u_int16_t from 'read' and it also passes u_int16_t to 'write', return value of 'write' is discarded. Seems like the interface is richer than what its caller actually uses. And it seems that implementations of the interface do not always have the exact signature - they have the same number of parameters, but the types are varying. Some implementations are closer to the interface contract, e.g. returning -1 from 'read' in case of error. Some are closer to the caller's expectations, e.g. having void return type in 'write'. What are your opinions - should the calling code be enhanced to use the interface properly (i.e. attempt to detect error conditions) or should the interface be dumbed down to its caller's expectations? My ultimate goal is to make all implementations have exactly the signature mandated by the interface. -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: diagnosing freezes (DRI?)
Hello. Just to let everyone know, I'm now coming to the conclusion that I may be suffering from hardware/thermal problems and that the DRI driver wasn't actually at fault (but highlighted the problem by pushing the hardware... harder). Thanks for the assistance, though. xw ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Problem: FreeBSD 7.x ssh v2 nss_ldap
On 04/15/2009 01:33 AM, Konrad Heuer wrote: I see a problem on two systems running FreeBSD 7.0 or 7.1 which are configured as OpenLDAP clients using the nss_ldap module. When someone logs on using ssh protocol version 2 the session will not be initialized correctly. The user will only get his primary group affiliation but no affiliation to other groups (memberUid attribute in LDAP group entries). On 7.1 the ssh login process hangs forever with open ldap queries, on 7.0 the group list is incomplete. On several 6.x systems, all works correctly. I have used the configuration for years now. There are some workarounds I found: a) use ssh protocol version 1 b) set UseLogin to yes in sshd_config c) avoid ssl encryption in communication to ldap server (ldap://... uri instead of ldaps://... in ldap.conf) Does anybody see similar problems? Does anybody have an idea what may couse the problem? I recently submitted ports/133501 regarding this issue, but I have not yet received a response. My workaround was to disable pthread_atfork support, so the problem might be related to the change from libkse to libthr in RELENG_7. -- Benjamin Lee http://www.b1c1l1.com/ signature.asc Description: OpenPGP digital signature
