jobs
| openssh-fuzz-cases | jobs | |
|---|---|---|
| 1 | 7 | |
| 5 | 192 | |
| - | 0.0% | |
| 0.0 | 0.0 | |
| about 3 years ago | over 1 year ago | |
| Roff | Go | |
| - | MIT License |
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.
openssh-fuzz-cases
-
Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
> As far as I know, the client is not fuzzed (though I'd be happy to find out I'm wrong).
Just touching on this one part, the rest still applies, openssh does use fuzzing. [0][1] Both client and daemon are fuzzed using AFL, though it does seem to be on an ad-hoc basis rather than automated, but it generally happens before a new release.
Unfortunately, to run AFL on openssh, they do have to patch it a bit, so what gets fuzzed and what is released isn't 1-to-1. This is because the privilege separations tend to defeat methods of detecting most of those sorts of bugs on their own.
[0] https://github.com/djmdjm/openssh-fuzz-cases
[1] For example: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ke...
jobs
- Apply for a job through SSH - $ ssh jobs.hackclub.com
- Apply for a job via SSH – $ ssh jobs.hackclub.com
-
Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
This is actually just a Go app which implements SSH using the Go standard library's SSH module. It's not like you're really SSH-ing into a server. See the source: https://github.com/hackclub/jobs
What are some alternatives?
sshtron - $ ssh sshtron.zachlatta.com
the-hacker-zephyr - 🚂 The Hacker Zephyr: A cross-country hackathon on a train! This repo: all of our planning documents, finances, and code open sourced.