Getting Involved in 0x00sec with GitLab

community
git
gitlab

(oaktree) #1

With the announcement of pupper and a few other things over these last few months, our collaborative effort is off to a nice start. Many of us regulars have been working together on a handful of projects. We’re now offering a place to put all those projects!

In order to draw in more of you, the Admins thought to make a little tutorial on how to get involved.

To start, please go to git.0x00sec.org and make an account.

You’ll see something like:

(Mine is black because I use a page-inversion browser plugin)

Make a new account! Confirm your email. Pretty straightforward. Here’s what you’ll see when you make a new account:

Click on Browse Projects at the bottom of that page. You’ll see the pupper repository. Right now, it’s the only Trending repo.

Here’s what that repository page looks like:

Whoops! What’s this…?

Looks like we need to add an ssh key! Easy enough. Here’s how [1]:

If you already have an SSH key, you can skip the key-generation steps.

$ ssh-keygen -t rsa -b 4096 -C "[email protected]"

It is important that you use whatever email you used to sign up on GitLab.

You’ll then see:

Enter a file in which to save the key (/Users/you/.ssh/id_rsa):

If you are making another SSH key, you will need to specify a new file name for this one. Otherwise, just hit [ENTER].

The program will then ask you for a passphrase. You can hit enter to leave it blank, but I highly recommend that you make a password for your SSH key(s).

You’ll then have to ensure that your ssh-agent is running. After, you must add your new key to the agent.

$ eval "$(ssh-agent -s)"
$ ssh-add ~/.ssh/id_rsa

Note: If you named your SSH key something different, specify that filepath instead.

Next, you’ll need this program (on linux):

$ sudo apt-get install xclip

Then, run

$ cat ~/.ssh/id_rsa.pub | xclip -selection c

It is very important that you copy your public key and NOT your private key. Guard your private key(s) as if they were your life!!!

Now that you have the key copied to your clipboard, navigate to your Profile Settings:

Then, head to the SSH Keys tab:

Paste your public key where it says to paste it. Give it a descriptive title so you know what that key is for or where that key is from.

Once you’re done, open ~/.ssh/config in your editor of choice and add:

Host gitlab.s-3.tech
  HostName gitlab.s-3.tech
  User git
  IdentityFile ~/.ssh/id_rsa
  Port 31337

If your ssh key has a different filepath or name, substitute ~/.ssh/id_rsa with that. Here, you’ll want to specify the path to your private key.

Alright, now you should be able to:

$ git clone [email protected]:pry0cc/pupper.git

We’re excited to see what comes of this.


Git Gud 001: Basic explanation & creating our first repo
(Command-Line Ninja) #2

Great job @oaktree! Really nice overview of how to do it. I was partially afraid that GitLab might’ve put some users off, although once you cut through the noise, it’s a really nice interface for Git.

Plus we have a lot of really cool projects going on our GitLab, it’d be a shame to see them go to waste :stuck_out_tongue:


(Exorust) #3

Honestly this is one of the most informative post! I am a newbie and without this post I really would have been lost. Thanks. :slight_smile:


(Command-Line Ninja) #4

ALSO, it seems it is down? @L0k1 @Suser what is that about?


(Not a N00b, but still learning) #5

Seems like they messed up the https cert by issuing it to https://gitlab.s-3.tech instead of https://git.0x00sec.org/
You can still use it either in a fresh browser installation(because of HSTS) or just click the s-3.tech link


(Command-Line Ninja) #6

Man you are a genius!

I must admit I didn’t dig very deep, Well done!