Reputation
Top tag
Next privilege 20 Rep.
Talk in chat
Badges
1 3
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 0 votes cast
Jul
26
awarded  Notable Question
Jun
13
asked Run EC2 instance into specific non-default VPC in random subnet
Feb
20
asked IAM policy for list, create and destroy instances and security groups
Oct
17
awarded  Popular Question
May
31
awarded  Popular Question
Sep
13
comment how to enable TLSv1.1 and TLSv1.2 on nginx Debian squeeze?
Thanks for responding Apart from updating nginx, would need to update the openssl package or version already supports 0.9.8o TLSv1.1 and TLSv1.2?
Sep
13
asked how to enable TLSv1.1 and TLSv1.2 on nginx Debian squeeze?
Apr
22
comment how to config monit for send mail alert apache restart
Yes, i have configured mailserver like another server that it sends monit alert mails
Apr
22
comment how to config monit for send mail alert apache restart
yes, I can send emails from the system without problems
Apr
22
asked how to config monit for send mail alert apache restart
May
16
comment Error with git archive --remote <repo>
But with that key, I can run git clone, git pulls, etc ... These commands should fail, right?
May
16
comment Error with git archive --remote <repo>
If I delete the ~/.ssh/config and run: ssh -p2022 gitosis@servername /bin/pwd I enter the password and the screen shows me: /srv/gitosis
May
16
comment Error with git archive --remote <repo>
On my computer I have the file ~/.ssh/config with the following information: host servername Port 2022 # I configured git server with this port IdentityFile ~/.ssh/my_key With this configuration, run: ssh gitosis@servername /bin/pwd The following error appears: ERROR: gitosis.serve.main: Unknown command denied
May
16
comment Error with git archive --remote <repo>
Yes, I can connect from random PC. In fact, I can work with Git repositories. For example, I can clone a repository on a local machine.
May
16
asked Error with git archive --remote <repo>
Jan
23
awarded  Student
Jan
23
comment how to deny “sudo su”
It's simple: In /etc/sudoers I have: % sudo ALL = (ALL) NOPASSWD: ALL The user "user1" belongs to group "sudo". Therefore, the user "user1" can run "sudo <command>". Therefore, "user1" can run the command "sudo su". I need that "user1" is sudoer, but can not execute the command "sudo su".
Jan
23
asked how to deny “sudo su”
Dec
23
comment Problem to monitor ssh service with M / Monit
connectivity between m / monit monit is correct and because only 1 service fails, ssh. Looking at your setup, I have the same. The problem is that other servers have the same configuration and does not fail.
Dec
22
asked Problem to monitor ssh service with M / Monit