Nerves Security

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
elixir

Research direction

No files, tests, or entry points are named. Start by reviewing the existing curriculum structure and the security considerations for Nerves devices, including the use of Livebook; done means a focused Nerves security module or set of lessons is added.

Written by the indexing model from the issue text.

Description

discussion elixir content new content

It would be handy to encompass more of the Elixir Ecosystem with this training, as such we should include a module or lessons regarding Nerves best practices as it relates to security.

This could include things like explicitly calling out the use of Livebook on Nerves devices and such.

I am not as familiar with Nerves under the hood as I'd like to be, so I would love to see a sponsor for this content.

Dominant language
Elixir
Stars
732
Forks
172
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erlef/elixir-secure-coding

All issues in erlef/elixir-secure-coding

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.