You might want to consider just open sourcing portions of your code that you believe could benefit from community involvement, and keep certain things proprietary. If that is an option you could have separate repos and…
If you are not feeling confident in approaching strangers to start conversations, you might be tempted to start every conversation with something like, “Hi. I don’t know anybody here and I was hoping to …”. It’s okay to…
How about requiring devices to implement key security-relevant features in an immutable way, such as via FPGA, so that attackers have no way of circumventing those features even post EoS.
You might want to consider just open sourcing portions of your code that you believe could benefit from community involvement, and keep certain things proprietary. If that is an option you could have separate repos and…
If you are not feeling confident in approaching strangers to start conversations, you might be tempted to start every conversation with something like, “Hi. I don’t know anybody here and I was hoping to …”. It’s okay to…
How about requiring devices to implement key security-relevant features in an immutable way, such as via FPGA, so that attackers have no way of circumventing those features even post EoS.