13.3 - bad $PATH being added by /etc/paths.d/10-cryptex

[luckman212]

I have a small function in my .bash_profile that validates all the $PATH entries on my system. First thing I noticed after today's 13.3 update were these 3 new invalid paths being set:

/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin

Anyone else seeing this? The /var/run/com.apple.security.cryptexd/codex.system/bootstrap/ directory does exist, but there's nothing in it.

These are coming from /etc/paths.d/10-cryptex and can be seen by running the following command:

eval "$(/usr/libexec/path_helper -s)"; tr : '\n' <<<"$PATH"

 

[Jim Macak]

I see this also. Someone recently reported this issue here:

Remnant PATH entries in macOS Venture 13.3 update

 

[fivenotrump]

These are not invalid. They are empty at present but likely to be used by Rapid Security Response updates.

 

[luckman212]

Future or not, they are invalid right now. None of the paths exist.

 

[fivenotrump]

They are to be used as mount points.

 

[PradeepKumar2002]

I have a small function in my .bash_profile that validates all the $PATH entries on my system. First thing I noticed after today's 13.3 update were these 3 new invalid paths being set:

/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin

Anyone else seeing this? The /var/run/com.apple.security.cryptexd/codex.system/bootstrap/ directory does exist, but there's nothing in it.

These are coming from /etc/paths.d/10-cryptex and can be seen by running the following command:

eval "$(/usr/libexec/path_helper -s)"; tr : '\n' <<<"$PATH"

Were you able to overcome this issue? If so, can you please share the details?

 

[luckman212]

@PradeepKumar2002 I was able to "overcome" the issue by just setting up a small function in my .bash_profile to remove/ignore them. But no, as of 13.5.1 these paths are still being set by the system, and they still don't exist