An issue has been found which was formed even before GitHub was established or Git was released. Take a look at it here
Ciro Santilli, a humble man has been commiting on GitHub for over 100 years. Unfortunately, his dedication was not preceived well by others and GitHub decided to hide his contributions. Take a look at his profile here
Usernames can extend vertically infinitely as well. Take a look at his mysterious profile here
Take a look at his profile here
Try out the following command:
git commit --date="Wed Feb 16 14:00 2011 +0100"
Check out the present Logical Awesome LLC site
On 26 March 2015, GitHub fell victim to a massive distributed denial-of-service (DDOS) attack that lasted for more than 118 hours. The attack, which appeared to originate from China, primarily targeted GitHub-hosted user content describing methods of circumventing Internet censorship.
Researchers had pored over dumped data allegedly belonging to a group associated with the NSA. The data, which contains a number of working exploits, was distributed via Dropbox, MEGA, and other file sharing platforms.
The files were also linked to from a page on Github, but the company removed it despite having hosted plenty of hacked material in the past. It turns out that removal was not due to government pressure, but because the hacker or hackers behind the supposed breach were asking for cash to release more data.
Anyone who has your access key has the same level of access to your AWS resources that you do. Consequently, we go to significant lengths to protect your access keys, and in keeping with our shared-responsibility model, you should as well.
Read the article here
Github has killed its search function to safeguard users who were caught out storing keys and passwords in public repositories. 'Users found that quite a large number of users who had added private keys to their repositories and then pushed the files up to GitHub. Searching on id_rsa, a file which contains the private key for SSH logins, returned over 600 results. Projects had live configuration files from cloud services such as Amazon Web Services and Azure with the encryption keys still included. Configuration and private key files are intended to be kept secret, since if it falls into wrong hands, that person can impersonate the user (or at least, the user's machine) and easily connect to that remote machine.' Search links popped up throughout Twitter pointing to stored keys, including what was reportedly account credentials for the Google Chrome source code repository. The keys can still be found using search engines, so check your repositories.
Read the article here
Need Assistance? View FAQ
Found something suspicious. Open an issue.