Initially taken by Niko Matsakis and lightly edited by Ryan Levick
- Introductions
- Cargo inside large build systems
- FFI
- Foundations and financial support
| use std::collections::{BTreeMap}; | |
| use std::fs::File; | |
| use std::io::{self, BufRead, Read, Seek, SeekFrom}; | |
| use std::ops::AddAssign; | |
| use fnv::FnvHashMap; | |
| #[derive(Debug, Clone, Copy)] | |
| struct TemperatureStats { | |
| min: f32, | |
| max: f32, |
| diff --git a/default.c b/default.c | |
| index dc3fa58..5e21015 100644 | |
| --- a/default.c | |
| +++ b/default.c | |
| @@ -2091,6 +2091,7 @@ int force_g = 0; | |
| unsigned char ggr_drv[MAX_STR_LEN] = ""; | |
| unsigned char ggr_mode[MAX_STR_LEN] = ""; | |
| unsigned char ggr_display[MAX_STR_LEN] = ""; | |
| +unsigned char embed[MAX_STR_LEN] = ""; | |
| # Put this function to your .bashrc file. | |
| # Usage: mv oldfilename | |
| # If you call mv without the second parameter it will prompt you to edit the filename on command line. | |
| # Original mv is called when it's called with more than one argument. | |
| # It's useful when you want to change just a few letters in a long name. | |
| # | |
| # Also see: | |
| # - imv from renameutils | |
| # - Ctrl-W Ctrl-Y Ctrl-Y (cut last word, paste, paste) |
GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.
You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.
$ python githubcloner.py --org organization -o /tmp/output