Re: Cross-building for i386 from amd64
On Mon, 25 Jan 2016, Daniel Eischen wrote: Is cross-building world for i386 from amd64 suppose to work? It doesn't in -stable. From reading the documentation out there, one of these should work: make TARGET=i386 buildworld make TARGET_ARCH=i386 buildworld What incantations do I need? The end result is I want multiple developers to be able to build nanobsd i386 images from amd64. I guess you can ignore this, I seemed to have hit a real compilation bug in -stable, which updating to the most recent -stable has fixed. FYI, I used: make TARGET_ARCH=i386 -j4 buildworld in -stable, and that worked. -- DE ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Cross-building for i386 from amd64
Is cross-building world for i386 from amd64 suppose to work? It doesn't in -stable. From reading the documentation out there, one of these should work: make TARGET=i386 buildworld make TARGET_ARCH=i386 buildworld What incantations do I need? The end result is I want multiple developers to be able to build nanobsd i386 images from amd64. -- DE ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD not booting on Raspberry with VGA 666
On 2016-01-25 19:00, Oliver Psotta wrote: Hello, FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160121-r294499 did not boot on a Rasberry Pi 2 B with the Gert VGA 666 adaptor connected to the Raspberry's GPIO port. This adaptor basically is a passive resistor network, using most of the GPIO's pins. FreeBSD doesn't support this kind of screen at the moment. My guess is that FreeBSD tries to activate the serial port on GPIO and this fails. Is there a solution to turn off the serial port or set the config.txt to enable booting? You will need to edit the dts file and recompile a new dtb that disable the serial port. By the way I've managed to get VGA 666 working for FreeBSD with the same settings and files as for Linux and Risc OS. Of course booting stops after the message [code] Hit any key to stop autoboot: 0 [/code] I guess it's works because u-boot and knows about it but as said before FreeBSD doesn't support this kind of screen. -- Emmanuel Vadot ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD not booting on Raspberry with VGA 666
Hello, FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160121-r294499 did not boot on a Rasberry Pi 2 B with the Gert VGA 666 adaptor connected to the Raspberry's GPIO port. This adaptor basically is a passive resistor network, using most of the GPIO's pins. My guess is that FreeBSD tries to activate the serial port on GPIO and this fails. Is there a solution to turn off the serial port or set the config.txt to enable booting? By the way I've managed to get VGA 666 working for FreeBSD with the same settings and files as for Linux and Risc OS. Of course booting stops after the message [code] Hit any key to stop autoboot: 0 [/code] ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HPN and None options in OpenSSH
On Mon, Jan 25, 2016 at 12:28:20PM +0100, Jan Bramkamp wrote:
>
>
> On 24/01/16 15:50, Dag-Erling Smørgrav wrote:
> > Slawa Olhovchenkov writes:
> >> Can you do some small discurs about ssh+kerberos?
> >> I am try to use FreeBSD with $HOME over kerberoized NFS.
> >> For kerberoized NFS gssd need to find cache file "called
> >> /tmp/krb5cc_, where is the effective uid for the RPC
> >> caller" (from `man gssd`).
> >>
> >> sshd contrary create cache file for received ticket called
> >> /tmp/krb5cc_XXX (random string, created by krb5_cc_new_unique). Is
> >> this strong security requirement or [FreeBSD/upstream] can be patched
> >> (or introduce option) to use /tmp/krb5cc_ as cache file for
> >> received ticket?
> >
> > I wasn't aware of that. It should be easy to patch, but in the
> > meantime, you can try something like this in .bashrc or whatever:
> >
> > krb5cc_uid="/tmp/krb5cc_$(id -u)"
> > if [ -n "${KRB5CCNAME}" -a "${KRB5CCNAME}" != "${krb5ccuid}" ] ; then
> > if mv "${KRB5CCNAME}" "${krb5ccuid}" ; then
> > export KRB5CCNAME="${krb5ccuid}"
> > else
> > echo "Unable to rename krb5 credential cache" >&2
> > fi
> > fi
> > unset krb5ccuid
>
> If $KRB5CCNAME is set during PAM session setup than the pam_exec module
> might allow a reliable implementation along those lines:
>
>- Stop if $KRBCCNAME is invalid (klist -t)
>- Stop if /tmp/krb5cc_$UID is already valid and has enough time left
>- Copy the ticket to /tmp and rename it to /tmp/krb5cc_$UID.
>
> Keep in mind that this approach leaves valid tickets in /tmp after the
> SSH session ends while OpenSSH normally does its best to tie forwarded
> tickets to a SSH session.
Please check me: you propose to add to /etc/pam.d/sshd string like
session requiredpam_exec.so /patch/to/some/scripts
and do above checks in this scripts?
'session' executed after 'account' phase, on 'account' phase NFS must
be already accessed (for checks presents some files in $HOME and
importing/executing/interpretating, like .login_conf, .k5login and
etc).
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HPN and None options in OpenSSH
On 24/01/16 15:50, Dag-Erling Smørgrav wrote:
Slawa Olhovchenkov writes:
Can you do some small discurs about ssh+kerberos?
I am try to use FreeBSD with $HOME over kerberoized NFS.
For kerberoized NFS gssd need to find cache file "called
/tmp/krb5cc_, where is the effective uid for the RPC
caller" (from `man gssd`).
sshd contrary create cache file for received ticket called
/tmp/krb5cc_XXX (random string, created by krb5_cc_new_unique). Is
this strong security requirement or [FreeBSD/upstream] can be patched
(or introduce option) to use /tmp/krb5cc_ as cache file for
received ticket?
I wasn't aware of that. It should be easy to patch, but in the
meantime, you can try something like this in .bashrc or whatever:
krb5cc_uid="/tmp/krb5cc_$(id -u)"
if [ -n "${KRB5CCNAME}" -a "${KRB5CCNAME}" != "${krb5ccuid}" ] ; then
if mv "${KRB5CCNAME}" "${krb5ccuid}" ; then
export KRB5CCNAME="${krb5ccuid}"
else
echo "Unable to rename krb5 credential cache" >&2
fi
fi
unset krb5ccuid
If $KRB5CCNAME is set during PAM session setup than the pam_exec module
might allow a reliable implementation along those lines:
- Stop if $KRBCCNAME is invalid (klist -t)
- Stop if /tmp/krb5cc_$UID is already valid and has enough time left
- Copy the ticket to /tmp and rename it to /tmp/krb5cc_$UID.
Keep in mind that this approach leaves valid tickets in /tmp after the
SSH session ends while OpenSSH normally does its best to tie forwarded
tickets to a SSH session.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
