This gist assumes:
| username: vagrant | |
| password: vagrant | |
| sudo apt-get update | |
| sudo apt-get install build-essential zlib1g-dev git-core sqlite3 libsqlite3-dev | |
| sudo aptitude install mysql-server mysql-client | |
| sudo nano /etc/mysql/my.cnf |
I've had the opertunity to try a variety of different server configurations but never really got around to trying HHVM with Magento until recently. I thought I would share a detailed walkthrough of configuring a single instance Magento server running Nginx + Fast CGI + HHVM / PHP-FPM + Redis + Percona. For the purpose of this blog post I'm assuming you are using Fedora, CentOS, or in my case RHEL 6.5.
Please note: I'm 100% open to suggestions. If you see something I did that needs to be done a different way, please let me know. I haven't included my Perconca my.conf file yet. I will shortly. Also I plan on trying this same test with HHVM 3.3 and PHP 7.
rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
rpm -Uvh http://mirror.webtatic.com/yum/el6/latest.rpm
| #### Magento Hosting Performance Benchmarks | |
| #### Executed by: JeroenVermeulen.eu / MagentoHosting.pro | |
| ## Example test command for 5 concurrent users hitting as fast as possible: | |
| ## siege --concurrent=5 --file=urls.txt --log=log.txt --time=60s --quiet --benchmark --internet | |
| ## The file urls.txt contains 5029 URLs based on sitemap.xml. | |
| ## Magento contains 5933 Total products. | |
| ## Magento has 4697 Enabled products. | |
| ## |
| <?php | |
| php artisan tinker | |
| $controller = app()->make('App\Http\Controllers\MyController'); | |
| app()->call([$controller, 'myMethodName'], []); | |
| //the last [] in the app()->call() can hold arguments such as [user_id] => 10 etc' |
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