Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

On 2016-10-18 05:25, li...@wrant.com wrote: Mon, 17 Oct 2016 18:00:39 +0200 Karel Gardas 1) use machine with proper ECC support Hello Karel, Please explain this "proper ECC support" for every laptop user out there? [..] Mon, 17 Oct 2016 21:48:47 +0800 Tinker

Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

Tue, 18 Oct 2016 08:43:39 +0800 Tinker > Hi Anton, > > You misread me - Hi Tinker, This was intentional, as SoftECC is what you'd relate to, in contrast to the hardware ECC (SECDED), see: https://en.wikipedia.org/wiki/ECC_memory After the article page below references

Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

Anton, On 2016-10-18 09:46, li...@wrant.com wrote: Hi Tinker, [..] How to trig some event logic when the system has become vegetable because of overload by the userland? You're referring here to a watchdog timer, as present in some (most) BMC controllers, this usually requires an OS timer

Full disk encryption by auto install

Hello everyone, Is full disk encryption via auto install script feasible? Has anyone tried this before? Maybe somebody can share pointers on what to watch out for if it's already been done. I was wondering how the full disk encryption password can be secured during auto install. Maybe somebody can

Re: Full disk encryption by auto install

This has been discussed previously... And recently. Search the mailing lists and you will find your answers. ⁣​ On Oct 17, 2016, 23:12, at 23:12, "Tito Mari Francis Escaño" wrote: >Hello everyone, >Is full disk encryption via auto install script feasible? Has

Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

Mon, 17 Oct 2016 18:00:39 +0200 Karel Gardas > 1) use machine with proper ECC support Hello Karel, Please explain this "proper ECC support" for every laptop user out there? I am not sure my system implements "proper ECC support", how to validate? Can you advise why OpenBSD

Re: How to both redirect to console and screen

On Mon, Oct 17, 2016 at 11:34:02AM +, Mik J wrote: > Hello, > It is possible to redirect the boot sequence to the console using > # cat /etc/boot.conf > set tty com0 > But then there is no screen output. How is it possible to have both of them ? > > > Thank you This does not answer your

Re: What are the security features in OpenBSD 6.0 that are by default disabled?

On Sun, Oct 16, 2016 at 08:37:54PM +0200, Peter Janos wrote: > use S for extras security at the expense of performance. Use other options > only if you know what you are doing and have specific needs. > BTW, ssh and sshd enable S by themselves. >   > -Otto Some background on the current state of

Re: What are the security features in OpenBSD 6.0 that are by default disabled?

On 14.10.16 22:48, Raul Miller wrote: On Fri, Oct 14, 2016 at 2:50 PM, thrph.i...@gmail.com wrote: " The only truly secure system is one that is powered off, cast in a block of concrete and sealed in a lead-lined room with armed guards - and even then I have my doubts."

Re: What are the security features in OpenBSD 6.0 that are by default disabled?

On Mon, 17 Oct 2016 14:38:00 +0300 Gregory Edigarov wrote: > On 14.10.16 22:48, Raul Miller wrote: > > On Fri, Oct 14, 2016 at 2:50 PM, thrph.i...@gmail.com > > wrote: > >> " The only truly secure system is one that is powered off, cast in > >> a

Re: How to both redirect to console and screen

Hello, It is possible to redirect the boot sequence to the console using # cat /etc/boot.conf set tty com0 But then there is no screen output. How is it possible to have both of them ? Thank you

Re: How to both redirect to console and screen

Hello, write in /etc/boot.conf stty com0 115200 # Set the correct baud rate for com port set tty com0 # Redirect output to console port com0 Edit your baudrate. For e.g. APU2 it's 115200, may differ from other pc's. -stefan Von:

How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

Sometimes a machine goes unresponsive. In this case, a non-ECC RAM machine. The reason could be that something in the hardware or kernel failed, e.g. a bit flip error [1]. In this case (for a non-kernel developer), tough luck, and the proper thing would be to reboot, and keep statistics

Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

1) use machine with proper ECC support 2) man sendbug -- and following it report your OpenBSD kernel misbehavior On Mon, Oct 17, 2016 at 3:48 PM, Tinker wrote: > Sometimes a machine goes unresponsive. In this case, a non-ECC RAM machine. > > The reason could be that

Re: How to both redirect to console and screen

On 2016-10-17, Mik J wrote: > Hello, > It is possible to redirect the boot sequence to the console using > # cat /etc/boot.conf > set tty com0 > But then there is no screen output. How is it possible to have both of them ? There's no dual-console support in OpenBSD.

Re: How to both redirect to console and screen

On Montag, 17. Oktober 2016 11:34:02 PYST Mik J wrote: > Hello, > It is possible to redirect the boot sequence to the console using > # cat /etc/boot.conf > set tty com0 > But then there is no screen output. How is it possible to have both of them > ? > > > Thank you what about doas script -a