Capability-Based Security for Redox: Namespace and CWD as Capabilities

#1

Post by ejplatzer » Fri, Mar 27, 2026, 7:06 PM UTC

Capability-Based Security for Redox: Namespace and CWD as Capabilities
redox-os.org

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#2

Post by als0 » Fri, Mar 27, 2026, 10:07 PM UTC

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#3

Post by iam_circuit » Sat, Mar 28, 2026, 12:06 AM UTC

[dead]

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#4

Post by ambicapter » Sat, Mar 28, 2026, 12:47 AM UTC

als0 wrote: post #2

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Could I get some examples? I'm interested in learning more.

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#5

Post by davexunit » Sat, Mar 28, 2026, 1:30 AM UTC

ambicapter wrote: post #4

als0 wrote: post #2

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Could I get some examples? I'm interested in learning more.

http://habitatchronicles.com/2017/05/what-are-capabilities/

https://files.spritely.institute/papers/spritely-core.html

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#6

Post by wmf » Sat, Mar 28, 2026, 3:11 AM UTC

ambicapter wrote: post #4

als0 wrote: post #2

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Could I get some examples? I'm interested in learning more.

https://www.cl.cam.ac.uk/research/security/capsicum/

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#7

Post by Icathian » Sat, Mar 28, 2026, 3:56 AM UTC

ambicapter wrote: post #4

als0 wrote: post #2

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Could I get some examples? I'm interested in learning more.

Cloudflare's developer platform uses them. That's what their "bindings" are.

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#8

Post by pugchat » Sat, Mar 28, 2026, 8:20 AM UTC

[dead]

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#9

Post by tuananh » Sat, Mar 28, 2026, 8:35 AM UTC

there's also capsudo by kaniini

https://github.com/kaniini/capsudo

Re: Capability-Based Security for Redox: Namespace and CWD as Capabilities

#10

Post by als0 » Sat, Mar 28, 2026, 10:10 AM UTC

ambicapter wrote: post #4

als0 wrote: post #2

Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.

Could I get some examples? I'm interested in learning more.

Implementations include seL4, Barrelfish, Google Fuchsia OS, Capsicum, and a slew of research systems too long to list. It's also worth checking out tangential things like the E programming language and Google's old Caja project.