Gary Guo
Gary Guo
yosys-slang maintainer expresses interest in taking the change upstream: https://github.com/lowRISC/ibex/pull/2309#discussion_r2366297282
The issue here is that for store instruction, both rs1 and rs2 are used. So if, say, we have `sd x31, 0(x10)`, then it should be illegal instruction. But since...
Feature request: relay traffic to unsafe routes to another peer (for running Kubernetes over Nebula)
It gives too much permission that otherwise it doesn't need. You essentially need to grant these nodes certificates that cover all subnets that may send traffic to them. In the...
Feature request: relay traffic to unsafe routes to another peer (for running Kubernetes over Nebula)
I've created #1496 with the implementation I have so far. Essentially https://github.com/slackhq/nebula/pull/1496/files#diff-82e703a5afa19816398fab9e88080a970082c81bcb3d11cd67a7b96b8f69a1bfR846-R871 would be all non-error if the certificate is just signed with all subnets.
Feature request: relay traffic to unsafe routes to another peer (for running Kubernetes over Nebula)
Unfortunately this still allows these nodes to impersonate other Nebula nodes. ```go // Try some cases where the address is *not* covered by certificate and ensure they're rejected. p =...
Feature request: relay traffic to unsafe routes to another peer (for running Kubernetes over Nebula)
We've evaluated out some alternative approaches suggested: 1. Running two Nebula instances, with one for node-to-node traffic and one for ingress -- this requires running multiple instance of lighthouses and...
Would `#![custom::foo]` be supported? Currently `custom_inner_attributes` feature is required even if `register_tool` is used to register the custom tool. Feels like it's worth mentioning in the RFC about this, regardless...