iovisor / iovisor/bcc

eBPF bytecode signing like kernel module signing

Open
#2,550 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
5d 13h
Merged PRs (30d)
3

Description

Hi all,

I have one question regarding eBPF bytecode. When bytecodes are generated in bcc, why are we not signing it for security reasons like kernel module is signed in linux as we are sending generated bytecodes to kernel, for verification. Has it ever been tried?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue discusses signing eBPF bytecode generated in bcc before sending it to the Linux kernel, analogous to kernel module signing. Start by investigating whether this has been tried and how kernel verification currently works; done would require a decided, technically scoped approach rather than answering the question alone.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.