Skip to content

Stellux posix cwd semantics#65

Merged
FlareCoding merged 7 commits intostellux-3.0-prototypingfrom
cursor/stellux-posix-cwd-semantics-ccac
Mar 4, 2026
Merged

Stellux posix cwd semantics#65
FlareCoding merged 7 commits intostellux-3.0-prototypingfrom
cursor/stellux-posix-cwd-semantics-ccac

Conversation

@FlareCoding
Copy link
Owner

Implement POSIX current working directory (CWD) semantics to enable relative path resolution and standard CWD syscalls.


Open in Web Open in Cursor 

cursoragent and others added 4 commits March 4, 2026 12:19
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
…ntics

Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
@cursor
Copy link

cursor bot commented Mar 4, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@FlareCoding FlareCoding marked this pull request as ready for review March 4, 2026 12:51
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
Co-authored-by: Albert Slepak <FlareCoding@users.noreply.github.com>
@FlareCoding FlareCoding merged commit 539c5d0 into stellux-3.0-prototyping Mar 4, 2026
15 checks passed
@FlareCoding FlareCoding deleted the cursor/stellux-posix-cwd-semantics-ccac branch March 4, 2026 13:50
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

return resolve_rc;
}
path_for_open = resolved_path;
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHM path check uses unnormalized path for absolute paths

Medium Severity · Security Issue

In do_open_common, when kpath is absolute, is_shm_path is checked against the raw unnormalized user path before normalizing. A path like /dev/shm/../../etc/passwd would pass the is_shm_path prefix check, then normalize_absolute_path resolves it to /etc/passwd, which is routed to resource::open as though it's an shm path. The relative-path branch correctly checks is_shm_path on the normalized path. The same issue exists in unlinkat for absolute shm paths.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants