Re: Change to init in -current?

Theodore Wynnychenko wrote: > Does this mean that getty is only allowed to access "/usr/bin/login," and that > my custom script is not in an allowed location after unveil "locks down" > getty? yes. > Obviously, my script is named autologin.sh and lives in /local; and it does > exist with

Re: Change to init in -current?

-Original Message- From: Theo de Raadt [mailto:dera...@openbsd.org] Sent: Saturday, November 10, 2018 7:57 PM To: t...@uchicago.edu Cc: misc@openbsd.org Subject: Re: Change to init in -current? Theodore Wynnychenko wrote: > So, to do this, I edited the appropriate terminal line in /

Re: Change to init in -current?

Theodore Wynnychenko wrote: > So, to do this, I edited the appropriate terminal line in /etc/ttys to a > custom > entry defined in /etc/gettytab; then added an entry to /etc/gettytab, using > 'lo:' to point to a ksh script which (basically) looks at the input given to > getty, and if it

Re: Change to init in -current?

You don't say how you updated to current. If you updated without a snapshot, it is possible you got caught up in a strange malloc change. it is also possible that some unveil / pledge things have broken your strange usage case, for instance maybe "lo" doesn't work anymore due to changes. You