Man In The Middle Attack

How the Hack Do I Use GitHub?

Dear Lifehacker,
I've learned to code and want to start using GitHub to manage my projects. Despite the introductory lesson they provide, I still don't understand how it works at all. Can you help me?

Sincerely,
Git Help

Dear GH,
GitHub's a great tool but it's definitely a little confusing the first time around (and, possibly, a few times after that). That's likely why GitHub created software (for OS X and Windows) to make the process a bit easier. Nevertheless, it's good to learn the old-fashioned way otherwise your options in the simplified software won't make sense. Let's start by walking through the basics.

---

Step One: Sign Up for GitHub

Here comes the easy part: make yourself a GitHub account signing up on the front page. After completing the form, GitHub will sign you in and take you to your empty news feed. In the middle of the page, you'll see the boot camp (pictured to the right). We're going to go through it to set up your account and, later, create your first repository. Click on "Set Up Git" to get started.

Step Two: Install Git

GitHub exists because of a version control application called.git The site is based on how git works, and git is pretty old. It runs via the command line and has no fancy graphical user interface. Since it's made to manage code you wrote, this shouldn't sound too scary. (Of course, as previously mentioned, GitHub did make wonderful software to allow you to use their service without the command line but that won't help you too much unless you know the basics.)

 

Git works by reading a local code repository (just a folder containing code for your project) on your computer and the mirroring that code elsewhere (in this case, GitHub's servers). Initially, we'll commit (i.e. send) your entire local repository to GitHub, but that's just a one-time affair. As you continue to work on your code, you'll simply commit changes. GitHub will then keep track of the changes you made, creating different versions of files so you can revert back to old ones if you want (or just keep track of those changes for other reasons). This is primarily why you'd want to use a version control system like git on your own, but additional benefits surface when using git to manage code with other people working on your project. When multiple developers commit code with git, GitHub becomes a central repository where all the code that everyone's working on can stay in sync. You'll commit your changes, and other developers will pull them (i.e. sync them to their local repository). You'll do the same with their code.

Git makes this all happen, so you need to download the latest version and install it. On OS X, you'll just install the command line app. On Windows, you'll get a few more items. We'll discuss how they work in the next step.

Step Three: Set Up Git

To set up git, you need to make your way into the command line. On OS X, that means launching the Terminal app (Hard Drive -> Applications -> Utilities -> Terminal) and on Windows, that means launching the Git Bash app you just installed—not the Windows command prompt. When you're ready, tell git your name like this:

git config --global user.name "Your Name Here"

For example, mine would look like this because I'm using a test account for this example:

git config --global user.name "Adam Dachis"

You can put in any name you like, but afterward, you'll need to input your email and that email must be the email you used when signing up for GitHub:

git config --global user.email "your_email@youremail.com"

If for whatever reason, you signed up for GitHub with the wrong email address, you'll need to change it.

Now, to avoid always entering your login credentials and generating SSH keys, you'll want to install the credential helper so your passwords are cached. If you're on Windows, download it and install it. If you're on OS X, you'll need to handle this through the Terminal. To start, use this command to download the credential helper:

curl -s -O \
http://github-media-downloads.s3.amazonaws.com/osx/git-credential-osxkeychain

This will download a tiny little file and shouldn't take too long. When finished, enter the following command to make sure the permissions are correct on the file you just download (and fix them if not):

chmod u+x git-credential-osxkeychain

Now it's time to install the credential helper into the same folder where you install git. To do so, enter this command:

sudo mv git-credential-osxkeychain `dirname \`which git\``

You'll be prompted for your administrator password because the above command began with sudo. Sudo is shorthand for "super user do" and is necessary when performing a task that requires root access. The sudo command allows you to become the root user (a user with permission to do pretty much anything) on your operating system for a moment so you can perform this task. You're asked to enter your password to prove you're an administrator on the computer and should be allowed to do this. Once you've entered your password and the credential helper has been moved, finish up the installation with this command:

git config --global credential.helper osxkeychain

Now you're all set and can move on to actually using git and GitHub!

Step Four: Create Your First Repository

Now that you've made it this far, you can actually use GitHub! As the first order of business, we're going to create a repository (or "repo" for short). Head on over to GitHub and click the "New Repository" button on the top right of your account page. (Note: If you're still displaying the GitHub Bootcamp section, it'll show up underneath it.)

When creating a repository you have a few things to decide including its name and whether it'll be publicly accessible or not. Choosing a name should be pretty simple because you likely already have a name for your project. If you're just following along for learning purposes, use "Hello-World." Why "Hello-World" and not "Hello World"? Because spaces and special characters will cause problems. Keep it simple and easy to type on the command line. If you want to include a more complex name, you can add it to the optional description field beneath the name field.

If you're creating an open-source project, you want a public repository. If you want to code by yourself or share only with specific people, a private repository will do. Make the choice that works best for you and your project.

When you're all done, you can click the "Create repository" button but you might want to do one other thing first: check the "Initialize this repository with a README" checkbox. Why? All repositories require a README file. Ideally, that file would contain a little information about your project, but you might not want to deal with that right now. By initializing the repository with a README, you'll get an empty README file that you can just deal with later. For the purposes of this tutorial, we're going to leave the box unchecked because, in the next section, we're going to create a README file from scratch to practice committing (sending) it to GitHub.

Step Five: Make Your First Commit

When you send files to GitHub, you commit them. To practice, we're going to initialize your local repository and create a README file to commit as practice. Before you start, you need to know where your local code repository is on your computer and how to access it via the command line. In this tutorial, we're going to assume there's a directory called "Hello-World" in your computer's home folder. If you need to create one, just run this command (same for Git Bash on Windows and OS X's terminal):

mkdir ~/Hello-World

Now change to that directory using the cd (change directory) command:

cd ~/Hello-World

In case you were wondering, the ~ represents your home directory in Git Bash and Terminal. It's simply shorthand so you don't have to type it all out (which would look more like /Users/yourusername/). Now that your repository is ready, type this:

git init

If you already had a repository ready to go, you'd just need to cd to that directory and then run the commandgit init in there instead. Either way, your local repository is ready to go and you can start committing code. But wait, you don't have anything to commit! Run this command to create a README file:

touch README

Let's take a break for a second and see what just happened. Go into the home folder on your computer and look at the Hello-World folder (or look at whatever folder you're using for a local repository). You'll notice a README file inside, thanks to the command you just ran. What you won't see is a .git folder, but that's because it's invisible. Git hides it in there, but because you ran the commandgit init you know it exists. If you're skeptical, just run the commandls in Git Bash/Terminal to display a list of everything in the current directory (which, if you're following along, is your local repository).

So how does it know we want to commit this README file we just created? It doesn't, and you have to tell it. This command will do the trick:

git add README

If you want to add other files to commit, you'll use the same command but replace README with the name of a different file. Now, run this command to commit it:

git commit -m 'first commit'

While the other commands were pretty straightforward, the commit command has a little more going on so let's break it down. When you type,git that's just telling the command line that you want to use the git program. When you type,commit you're telling it you want to use the commit command. Everything that follows those two thing counts as options. The first, -m, is what's known as a flag. A flag specifies that you want to do something special rather than just run the commit command. In this case, they flag means "message" and what follows it is your commit message (in the example, 'first commit'). The message isn't absolutely necessary (although you'll usually need to provide one), but simply a reference to help you differentiate the various versions of a file (or files) you commit to your repository.

Your first commit should go by in a split second because you haven't actually uploaded anything yet. To get this empty README file to GitHub, you need to push it with a couple of commands. Here's the first:

git remote add origin https://github.com/yourusername/Hello-World.git

You need to replace "yourusername" with—you guessed it—your GitHub username. For me, it'd look like this:

git remote add origin https://github.com/gittest1040/Hello-World.git

This command tells git where to send your Hello-World repository. Now all you need to do is send it:

git push origin master

Once you run that command, everything (in this case, just your README file) will make it's way over to GitHub. Congratulations on your first commit!

Learning More

Using GitHub requires more than just committing a README file, but these basics should give you a good grasp on how to interact with the git app and the service. Now that you know how GitHub works at its core, you can use the GitHub apps to manage your code instead if you prefer. If you want to learn more about GitHub, there are some great tutorials. For starters, take a look at how to fork a repository and LockerGnome's GitHub guide.

Have fun to manage your code!

Love,

More Information

Related Post

1. How To Hack Website
2. How to hack WiFi | WiFi Hacking
3. HOW TO HACK WHATSAPP | HACK ALL PHONE CALL AND MESSAGES WITHOUT SS7 ATTACK
4. ☆ #HACKING #ANDRIOD GAME
5. Google Dorks : Use Google For Hacking websites, Databases and Cameras

Also Read

1. 100 working deep web, onion and dark web links
2. How to Change Your IP Address (Windows)
3. XSS-keylogger – keylogging script that can be injected into websites vulnerable to cross-site scripting

Use JPGFileBinder to Hide Files Inside JPEG Images Easily

We discussed how to hide files inside JPEG/GIF/PNG images in Windows PCs in a previous article. The method was not difficult but it involves some hassle. It includes making a new folder and copying files through the command line.

There is a tool known as JPGFileBinder which can be used for the same purpose. The software is portable and requires no installation. You can easily hide files inside JPEG images using this tool. All you need to do is download the zip file, extract the JPG+FileBinder.exe in your computer and hide files using a few steps.

Here’s a step by step guide to perform the process.

1. Collect the files which you want to hide in a single folder because you would need to compress it to .rar or .zip format using a file compression tool.

2. Double click on JPG+FileBinder.exe icon.

3. A small pop up box will appear. Click on the “Picture” button to add a picture in which you want to hide files. Click on “Compressed file” button to add files you compressed in step 1.

4. Click on “Output Picture File” button. Now you have to give a name to the output picture file. This output file will be your secret image file in which all the compressed files will stay hidden.

Note: In the example, I’ve given a name “picture” to the image file. It will be saved as picture.jpg. You are free to choose any other name.

5. Now click on OK button.

6. A small notification box appears telling you that the files have been binded.

How to get our Files back from the image

In step 5, a name has been given to the output picture file. Rename the output image file picture.jpg to picture.zip. Now open it using any file compression software such as Zipgenius, 7Zip, Winrar or extract it online using Wobzip.

Download JPGFileBlinder [Softpedia via Makeuseof]

More Information

How To Send An Anonymous Email Bomber Online 2017

How To Hack Website

How To Hack Wifi

How To Hack WhatsApp

How To Hack Any Android Game

How To Hack Website, Database & Camera using Gogle

How to Become a Hacker

In computer security, a hacker is someone who focuses on security mechanisms of computer and network systems. There are a community and shared culture of expert programmers and networking wizards that trace its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture were the first "hackers." Breaking into computers and breaking phone systems have come to symbolize hacking in popular culture, but hacking culture is much more complex and moralistic than most people know. To become a hacker, learn basic hacking techniques, how to think like a hacker, and how to gain respect within the ethical hacking community.

Part1

Learning Fundamentals

1. 
   1
   Run a UNIX-like OS, such as Linux. UNIX and UNIX-like operating systems are the operating systems of the Internet. While you can learn to use the Internet without knowing UNIX, you can't be an Internet hacker without understanding UNIX. For this reason, the hacker culture today is pretty strongly UNIX-centered. There are many types of UNIX-like operating systems, the most popular being Linux, which you can run alongside Microsoft Windows on the same machine. Download Linux online or find a local Linux user group to help you with installation.^[1]

   • A good way to dip your toes in the water is to boot up what Linux fans call a live CD or USB, a distribution that runs entirely off a CD or USB without modifying your hard disk. This is a way to get a look at the possibilities without having to do anything drastic.
   • There are other UNIX-like operating systems besides Linux, such as the *BSD systems. The most popular *BSD systems are FreeBSD, NetBSD, OpenBSD and Dragon Fly BSD. All are open source just like Linux, however, it's important to remember that they are BSD and not Linux.
   • MacOS is based on Darwin, a UNIX operating system that's based on FreeBSD. Darwin is fully free and open source and is available from http://opensource.apple.com. Because the core of the system is UNIX, and macOS is very popular, many people have ported over Linux applications to macOS. You can get those programs with a package manager like homebrew, fink or MacPorts. Alternatively, you can just run Linux on a Mac alongside macOS.
   • If you want to get super niche, you can even run an operating system like Open Indiana, which is based on the open source release of the Solaris operating system before it was acquired by Oracle and made closed source. OpenIndiana and Solaris are based on UNIX System V, and, as such, are not compatible with Linux applications. That said, there are many ports of Linux applications. You're probably better off just using macOS, BSD or Linux because they are much more popular and have many more programs available for them.
2. 
   2
   Write HTML. If you don't know how to program, learning basic HyperText Mark-Up Language (HTML) and gradually building proficiency is essential. What you see when you look at a website of pictures, images, and design components is all coded using HTML. For a project, set out to learn how to make a basic home page and work your way up from there.

   • In your browser, open the page source information to examine the HTML to see an example. Go to Web Developer > Page Source in Firefox and spend time looking at the code.
   • You can write HTML in a basic word processing program like Notepad or Simple text and save your files as "text only," so you can upload them to a browser and see your work translated.^[2]
   • You'll need to learn to format tags and learn to think visually using them.^[3] "<" is used to open a tag and "/> is used to close it. "
     " is the opening for a line of paragraph code. You'll use tags to signal anything visual: italics, formatting, color, etc. Learning HTML will help you to understand better how the Internet works.
3. 
   3
   Learn the language of programing. Before you start writing poems you have to learn basic grammar. Before you break the rules you have to learn the rules. But if your ultimate goal is to become a hacker, you're going to need more than basic English to write your masterpiece.

   • Python is a good "language" to start off with because it's cleanly designed, well documented, and relatively kind to beginners. Despite being a good first language, it is not just a toy; it is very powerful, flexible, and well-suited for large projects. Java is an alternative, but its value as a first programming language has been questioned.^[4]
   • If you get into serious programming, you will have to learn C, the core language of Unix. C++ is very closely related to C; if you know one, learning the other will not be difficult. C is very efficient with your machine's resources but will soak up huge amounts of your time on debugging and is often avoided for that reason, unless the efficiency of your computer is especially important.
   • It is probably a good idea to use a good starting platform such as Backtrack 5 R3, Kali or Ubuntu 12.04LTS.

Part2

Adopting Hacking Attitudes

1. 
   1
   Think creatively. Now that you've got the basic skills in place, you can start thinking artistically. Hackers are like artists, philosophers, and engineers all rolled up into one. They believe in freedom and mutual responsibility. The world is full of fascinating problems waiting to be solved. Hackers take a special delight in solving problems, sharpening their skills, and exercising their intelligence.

   • Hackers have a diversity of interests culturally and intellectually, outside of hacking. Work as intensely as you play, and play as intensely as you work. For true hackers, the boundaries between "play," "work," "science," and "art" all tend to disappear or to merge into a high-level creative playfulness.
   • Read science fiction. Go to science fiction conventions, which is a great way to meet hackers and proto-hackers.
   • Consider training in a martial art. The kind of mental discipline required for martial arts seems to be similar in important ways to what hackers do. The most hacker-ly martial arts are those which emphasize mental discipline, relaxed awareness, and control, rather than raw strength, athleticism, or physical toughness. Tai Chi is a good martial art for hackers.
2. 
   2
   Learn to love solving problems. No problem should ever have to be solved twice. Think of it as a community in which the time of everyone is hackers is precious. Hackers believe sharing information is a moral responsibility. When you solve problems, make the information public to help everyone solve the same issue.

   • You don't have to believe that you're obligated to give all your creative product away, though the hackers that do are the ones that get the most respect from other hackers. It's consistent with hacker values to sell enough of it to keep you in food and rent and computers.
   • Read older pieces, such as the "Jargon File" or "Hacker Manifesto" by The Mentor. They may be out of date in terms of technical issues, but the attitude and spirit are just as timely.^[5]
3. 
   3
   Learn to recognize and fight authority. The enemy of the hacker is boredom, drudgery, and authoritarian figures who use censorship and secrecy to strangle the freedom of information. Monotonous work keeps the hacker from hacking.

   • Embracing hacking as a way of life is to reject so-called "normal" concepts of work and property, choosing instead to fight for equality and common knowledge.
4. 
   4
   Be competent. So, anyone who spends time on Reddit can write up a ridiculous cyberpunk username and pose as a hacker. But the Internet is a great equalizer and values competence over ego and posture. Spend time working on your craft and not your image and you'll more quickly gain respect than modeling yourself on the superficial things we think of "hacking" in popular culture.

5. Part3

   Hacking Well

   1. 

       

       
      1
      Write open-source software. Write programs that other hackers think are fun or useful, and give the program sources away to the whole hacker culture to use. Hackerdom's most revered demigods are people who have written large, capable programs that met a widespread need and given them away so that now everyone uses them.
   2. 
      2
      Help test and debug open-source software. Any open-source author who's thinking will tell you that good beta-testers (who know how to describe symptoms clearly, localize problems well, can tolerate bugs in a quickie release, and are willing to apply a few simple diagnostic routines) are worth their weight in rubies.

      • Try to find a program under development that you're interested in and be a good beta-tester. There's a natural progression from helping test programs to helping debug them to helping modify them. You'll learn a lot this way, and generate goodwill with people who will help you later on.
   3. 
      3
      Publish useful information. Another good thing is to collect and filter useful and interesting information into web pages or documents like Frequently Asked Questions (FAQ) lists, and make those generally available. Maintainers of major technical FAQs get almost as much respect as open-source authors.
   4. 
      4
      Help keep the infrastructure working. The hacker culture (and the engineering development of the Internet, for that matter) is run by volunteers. There's a lot of necessary but unglamorous work that needs to be done to keep it going — administering mailing lists, moderating newsgroups, maintaining large software archive sites, developing RFCs and other technical standards. People who do this sort of thing well get a lot of respect, because everybody knows these jobs are huge time sinks and not as much fun as playing with code. Doing them shows dedication.
   5. 
      5
      Serve the hacker culture itself. This is not something you'll be positioned to do until you've been around for a while and become well-known for one of the four previous items. The hacker culture doesn't have leaders, exactly, but it does have culture heroes and tribal elders and historians and spokespeople. When you've been in the trenches long enough, you may grow into one of these.

   • Hackers distrust blatant ego in their tribal elders, so visibly reaching for this kind of fame is dangerous. Rather than striving for it, you have to sort of position yourself so it drops in your lap, and then be modest and gracious about your status.

   
   

More

How to hack website

Beginner SQL Tutorial

How to hack WiFi | WiFi Hacking

Top Best Hacking Tools Of 2017 For Windows, Linux and Mac OS X

Kali Linux Commands

☆ #HACKING #ANDRIOD GAME

Google Dorks : Use Google For Hacking websites, Databases and Cameras

Top 10 Hacking Tools

Which programming languages are useful for hacking