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 appropriate file permissions. It appears that getty does not have > access to it any longer. I surmise this error is because getty's filesystem > access has been locked down by unveil. > > Is that what was meant by "unveil of /usr/bin/login specifically," or is it > something else? yes. > Also, I am assuming that the only way I could correct this for myself would be > to learn a lot more of C than I know now, edit the getty source, and compile > it > locally. In other words, there isn't something I can do from the command line > to get it to work again, is there? yes. the C involved is actually very rudimentary. just look for calls to unveil in the source. the downside is this isn't likely to be a change taken back.
