Install, build and debug a react native app in WSL2 (Windows Subsystem for Linux) and Ubuntu.
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
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
var databaseUrl = "mongolaburl"; // "username:[email protected]/mydb" | |
var collections = ["Persons"]; | |
var db = require("mongojs").connect(databaseUrl, collections); | |
//Find a Person | |
db.Persons.find({sex: "male"}, function(err, users) { | |
if( err || !users) console.log("No male users found"); | |
else users.forEach( function(maleUser) { | |
console.log(maleUser); | |
} ); |