User Details
- User Since
- Jul 22 2022, 12:24 AM (123 w, 2 d)
Wed, Nov 27
Tue, Nov 5
Apr 10 2024
Apr 8 2024
Apr 7 2024
Mar 18 2024
Mar 17 2024
Hey @jrm, efnet seems to be down so I can't ask you this over IRC. I keep getting freefall build failures for i386-quarterly. Would it be ok to push my changes to the relevant quarterly branches?
Update manual page .Dd date
Update manual page .Dd date
- Included portfmt's suggestions thanks to Joe
- Version change from v0.17.0 to v0.17.1
Mar 10 2024
- Record *namei* violations instead of vfs. Slight wording change for clarity.
- Rebase on main after several months
- Rename all instances of CAPFAIL_VFS to CAPFAIL_NAMEI
- Rebase on main after several months
- Address Mark's comments
- Rebase on main after several months
Jan 9 2024
Replace all instances of "AT_FDCWD" with "<AT_FDCWD>" when reporting a violation via ktrcapfail().
Jan 7 2024
Actually, scratch that. I just understood your comment and this is a better solution.
It feels wrong to return inside of a macro, but I did not see any comments about it in style(9). This seems to be the solution that is most elegant in minimizing code duplication. Let me know your thoughts.
Jan 6 2024
@jrm Would you mind pushing this? I'm on vacation and forgot to copy my ssh key from my desktop before I left. Sigh.
Jan 5 2024
- Update version from 0.16.2 to 0.16.3.
- Add NOT_FOR_ARCHS=i386 to avoid building on i386.
I read through the pkg-fallout logs and I think the build failure on i386 is a FreeBSD Rust issue, unrelated to this port. I do not have the time to debug this further right now, so I'm going to add the NOT_FOR_ARCHS=i386 line.
Jan 4 2024
Jan 3 2024
Nov 17 2023
Nov 16 2023
Hey @markj. Need approval to commit.
Nov 15 2023
Nov 4 2023
Nov 3 2023
Oct 15 2023
Oct 5 2023
I created this patch to make the Capsicumization experience less intimidating for inexperienced developers. Both David and Mariusz may not be the target audience for this change because they already know how to extract the information that the tracing provides. Developers that are unfamiliar with Capsicum's semantics could use this tracing mode to easily determine why their program is not working in capability mode. I think it provides a solid starting point so new developers don't get lost and discouraged.
Sep 28 2023
Again, maybe I just need some more context to understand the reasoning behind this change.
Sep 4 2023
Sep 3 2023
Reword comment to say the namespace instead of just namespace.
Update to avoid rebase conflicts.
Update to avoid rebase conflicts.
Create a new cap_filed structure and accompanying cfiled SLIST for filed integrity verification in libcasper's cap_p_open().
Create filed nvlist directly from readconfigfile() and address Mark's comments.
Sep 1 2023
Add comment explaining intentional namespace pollution.
This patch has been applied to src under commit af93fea710385b2b11f0cabd377e7ed6f3d97c34.
Aug 30 2023
This patch was getting long, as @bsdimp pointed out. Split it into three separate patches. This patch will still define the locking regime.
Aug 29 2023
Include <sys/time.h> instead of <sys/timespec.h>. This causes intentional namespace pollution that mimics Linux.
Aug 28 2023
- Remove locking around knlist_add() and set islocked arg to 0
- Add space under declarations in timerfd_getboottime()
Aug 27 2023
Aug 26 2023
- Do not initialize tfd_lock with MTX_RECURSE.
- Add assertion in filt_timerfdread(), showing that the tfd_lock is held.
- Place tfd_count in kn->kn_data.