Re: How boot HDD-side crypto softraid from (bootable) USB disk? (AMD64/ARM. Currently installboot fails with "cross-device install"!..)

2017-02-05 Thread Tinker
Bytevolcano, Maybe I have a more effective solution at hand, what do you think about this: The following is for AMD64 though I'd guess that a similar approach would be possible on other platforms also. The boot sequence with MBR is: MBR: Load PBR (unencrypted) PBR: Load /boot

Re: How boot HDD-side crypto softraid from (bootable) USB disk? (AMD64/ARM. Currently installboot fails with "cross-device install"!..)

2017-02-05 Thread bytevolcano
There is still an elephant in the room. What if someone has physical access to your machine's USB ports, and decides to boot something nasty from it, which in turn modifies the firmware in your system (very likely to be possible due to stupid "consumer-grade" junk like UEFI or OS-flashable BIOS

Re: How boot HDD-side crypto softraid from (bootable) USB disk? (AMD64/ARM. Currently installboot fails with "cross-device install"!..)

2017-02-05 Thread Tinker
Bump! Again: How use a HDD as crypto softraid root filesystem media, but put boot code and cryto softraid keydisk partition (and perhaps /boot file and/or kernel) on an USB disk? Thanks, Tinker On 2017-02-02 10:27, Tinker wrote: Hi! I would like to have my system set up as follows: * My

surf2-0.6.20160922p0 segmentation fault on -current (#155) on i386

2017-02-05 Thread Jan Vlach
Hello openbsd-misc, I'm trying to move away from surf towards surf2 on my Asus EeePC, but surf2 segfaults on right at start. Deleting ~/.surf does not help. $ surf2 Segmentation fault (core dumped) --->8--- (gdb) backtrace #0 L1 () at /usr/src/lib/libc/arch/i386/string/strchr.S:16 #1

Re: dkimproxy broken after perl 5.24.1

2017-02-05 Thread Stuart Henderson
CCing a few lists in the hope that more people will see it. On 2017/02/05 20:47, Heiko wrote: > Hello, > > dkimproy and amavis broken with new per version: > > # /usr/local/bin/dkimproxy.out --daemonize > perl:/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/Crypt/OpenSSL/Bignum/Bignum.so:

Re: Huawei E353 as HiLink device

2017-02-05 Thread Karl Pettersson
On Sun, Feb 05, 2017 at 12:46:51PM +, Stuart Henderson wrote: > On 2017-02-03, Karl Pettersson wrote: > > I have a Huwaei E353 USB device, which I use to connect with the tre.se > > Internet provider. This device initially attaches as a mass storage > > device

Re: Huawei E353 as HiLink device

2017-02-05 Thread Stuart Henderson
On 2017-02-03, Karl Pettersson wrote: > I have a Huwaei E353 USB device, which I use to connect with the tre.se > Internet provider. This device initially attaches as a mass storage > device with product id 1f01. Under Linux, it is then switched to HiLink >

Re: pkg_add: ftp: connect: Invalid argument

2017-02-05 Thread Stuart Henderson
On 2017-02-05, jungle boogie wrote: > On 02/04/2017 07:17 PM, Philip Guenther wrote: >>> Is this it? >>> >>> "Trying 129.128.5.191... >> ... >>> 80377 ftp CALL connect(3,0xaf766dd0bf0,16) >>> 80377 ftp STRU struct sockaddr { AF_INET, 129.128.5.191:80 } >>>