> Eventually there will protocol or text side bug in xterm, and someone
> will figure out ways to escalate beyond our other mitigations. Rather
> than forcing them to operate inside an uncomfortable less-than-POSIX
> pledge+unveil environment, they can reuse a simple 1996-era shell-egg to
> execve
hem in might not be a good idea.
ig0r
ted text in the terminal to an
external program. This highlighted text could be a relative path to be
opened by the external program and thus requires a cwd.
I'm sure there are other people who use exec-formatted or other xterm
functions that rely on cwd who could benefit from this change.
ig0r
The current implimintation of ProcGetCWD relies on procfs. The following
patch uses sysctl to instead retrieve the current working directory.
This enables the use of exec-formatted xterm function on a path relative
to the terminal's current working directory.
ig0r < ig0r [at] b3zdna [
