openssl aes-256-cbc -k "$password" -d -a -in my_key.enc -out my_deploy_key Then use the $password file to decrypt your deploy key at integration-time, by adding to your yaml file: before_script: $ travis encrypt -add password=$password -r my-github-user/my-repo $ cat my_key | openssl aes-256-cbc -k "$password" -a > my_key.enc Here's a sketch of how the technique works.įirst generate an RSA deploy key (via ssh-keygen) called my_key and add it as a deploy key in your github repo settings. If you want to tighten down access (with a bit more work!) you can use GitHub deployment keys combined with Travis encrypted yaml fields. Note that sigmavirus24's response requires you to give Travis a token with fairly wide permissions - since GitHub only offers tokens with wide scopes like "write all my public repos" or "write all my private repos". To avoid handing over "the keys to the castle". Password: put me on the right track with the documentation link.) I read in lots of places that I needed to delete and recreate the remote, but in fact my normal push command worked exactly the same as the clone above, and the remote did not change: $ git push I was actually forced to enable two-factor authentication by company policy while I was working remotely and still had local changes, so in fact it was not clone I needed, but push. After about an hour of trawling documentation and Stack Overflow, I finally found the answer: $ git clone Laughably, the article tells you how to create it, but gives absolutely no clue what to do with it. git/config file in plain text, which is a security risk.įirst, you need to create a personal access token (PAT). If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your. Warning: Tokens have read/write access and should be treated like passwords. Git remote set-url origin will fix your project to use a remote with credentials built in. Unfortunately, however, you have no control over how Travis clones your repository, so you have to edit the remote like so. That will add your credentials to the remote created when cloning the repository. (Taking a look, however, indicates that it is not.) What you would normally do is the following: git clone -branch=gh-pages gh-pages That aside, that doesn't authorize your computer to clone the repository if in fact it is private. You should be using the following curl -H 'Authorization: token '. Join the nixCraft community via RSS Feed, Email Newsletter or follow on Twitter.Your curl command is entirely wrong. He wrote more than 7k+ posts and helped numerous readers to master IT topics. Vivek Gite is the founder of nixCraft, the oldest running blog about Linux and open source. Apache (2.0.46 and later) enables core dumps on Linux 2.4 and beyond, but only if you explicitly configure a CoreDumpDirectory. If Apache starts as root and switches to another user, the Linux kernel disables core dumps even if the directory is writable for the process. We are also using FreeBSD for testing and it write core dump in the ServerRoot directory. Another interesting fact I noticed that you need to configure Core Dumps on Linux only. I hope that I will get a new patched version of Apache by next week. Read man page of gdb for more information. Well I am not a developer but they are using gdb and other techniques to analyses the core dumps. # ls /tmp/apache2-gdb-dump How do I read the core dump files created by Apache on Linux systems? Now you should see core dumps in /tmp/apache2-gdb-dump directory: Please replace it with your actual Apache user:group combination. Please note that we are using httpd user and group appserver. # chown httpd:appserver /tmp/apache2-gdb-dump So all I need to do is put line as follows in nf:Ĭreate a directory /tmp/apache2-gdb-dump: This controls the directory to which Apache attempts to switch before dumping core. Apache Core DumpĪpache supports CoreDumpDirectory directive. ![]() To get rid of this problem I was asked to configure a Linux system so that Apache can dump core files on segmentation faults. The problem is that our application development team has hacked (aka modified source code) Apache 2.0 source tree for application my company developing. Apache/2 (WebAppBETA) child pid 1301 exit signal Segmentation fault (11) Apache/2 (WebAppBETA) child pid 1256 exit signal Segmentation fault (11)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |