check-spelling
fprime
check-spelling | fprime | |
---|---|---|
2 | 73 | |
241 | 9,894 | |
2.9% | 0.5% | |
7.8 | 9.2 | |
3 days ago | 4 days ago | |
Shell | C++ | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
check-spelling
-
Add check-spelling to a repository
View on GitHub
-
GitHub Actions checkspelling community workflow GitHub_TOKEN leakage via symlink
> If my repo always runs all tests on a PR, could someone just add a PR with a new test that is then run? Thus running their arbitrary code.
Running arbitrary code is inevitable if an action is configured to run on all PRs. People have abused this to run crypto miners and stuff in the past, but this for the most part is merely an annoyance to maintainers, not a security problem. It does become a security problem when arbitrary code execution is allowed with your secrets, including your configured secrets and the read/write GITHUB_TOKEN.
Expanding on the topic of secrets, if you trigger your test from the usual pull_request event, the workflow won't have access to GITHUB_TOKEN or configured secrets, so it's the safe default you should almost always choose. That becomes a problem when you need write access to the repo, e.g. to assign labels or add comments to the PR from the workflow, in which case you have to use the privileged pull_request_target event to expose GITHUB_TOKEN and secrets. pull_request_target by default runs in the context of the base of the PR, so there's still no arbitrary code, but you can explicitly check out the PR in that context, and when you do, your secrets are potentially exposed to arbitrary code. If you execute that arbitrary code in any job, or like in this case, post the content of effectively any file on disk as directed by an attacker, boom, owned.
Therefore, you should
- Avoid pull_request_target unless white access to the repo and/or access to configured secrets is absolutely necessary;
- When using pull_request_target, avoid checking out untrusted code;
- If it's absolutely necessary to check out untrusted code, make absolutely sure that the untrusted code isn't executed in any way, and that your trusted handling code can't be tricked by untrusted content in any way, like an arbitrary symlink. This is of course difficult to verify.
In this specific case, the fix seems to be checking that the absolute path of the untrusted advice.txt is within GITHUB_WORKSPACE (https://github.com/check-spelling/check-spelling/commit/4363...). IMO that's a wrong fix only covering the symptom. The real cause is using untrusted configuration files at all; why not make a copy of the trusted version of configuration files and use those instead???
GitHub has an article about security considerations here: https://securitylab.github.com/research/github-actions-preve...
fprime
- Fprime – A flight software and embedded systems framework by NASA
- F Prime – Flight software framework by NASA
- F': NASA Ingenuity Open-Source Flight Software Framework
-
Help finding flight software learning resources
Does anyone have any suggestions for learning to write flight software or have any resources to learn from? I'm not necessarily looking for a framework to learn either, unless you think I should be focusing on something like https://nasa.github.io/fprime/. At this point, I don't know what I don't know... what should I be focusing on?
-
What version of C++ does JPL use?
F´ (F Prime) is originally developed at JPL, which is written under the C++11 standard. The linked video should be based on JPL Institutional Coding Standard for the C Programming Language, which is a guideline for C. They should be using C++11 nowadays.
- GitHub - nasa/fprime: F' - A flight software and embedded systems framework
- Mars-Hubschrauber Ingenuity übertraf alle Erwartungen: Die kleine Helikopterdrohne begleitet den Rover Perseverance seit zwei Jahren – niemand hätte gedacht, dass er so lange durchhält
-
Mars Ingenuity helicopter breaks record for speed and altitude, NASA says
The navigation camera is something you can buy online, the other terrain camera is a Sony IMX 214, The flight software is on github, the altimeter is from sparkfun.
-
[ANN] NASA's Ogma -- now with FPrime support
[1] https://github.com/nasa/fprime
-
NASA should switch to Arch, bro 😎
Probes and satellites either user custom made os, or proprietary real time OS like VxWorks, or more recently open source fprime.
What are some alternatives?
did_you_mean - The gem that has been saving people from typos since 2014
ardupilot - ArduPlane, ArduCopter, ArduRover, ArduSub source
advisories
cFS - The Core Flight System (cFS)
PHP-Spellchecker - 🐘🎓📝 PHP Library providing an easy way to spellcheck multiple sources of text by many spellcheckers
Awesome-Linux-Software - 🐧 A list of awesome Linux softwares
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
Visual Studio Code - Visual Studio Code
Windows Terminal - The new Windows Terminal and the original Windows console host, all in the same place!
seL4 - The seL4 microkernel
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Netdata - The open-source observability platform everyone needs