194 reputation
8
bio website
location Athens, Greece
age
visits member for 2 years, 1 month
seen Nov 19 at 12:48
Developer

Apr
12
comment Why BIND does not use the forwarders any more?
Checked the logs, no hint there. I am confident that for some reason the forwarder I used so far (Norton ConnectSafe: 199.85.126.20) does not work with the above options. When I switched to OpenDNS it worked. The strange thing is that Norton ConnectSafe works when in resolv.conf (you may check it if you want).
Apr
10
comment Why BIND does not use the forwarders any more?
Added all the options suggested, still no luck. From what I see, bind always uses the root servers to resolve. Added "recursion yes" well, still no luck.
Mar
29
comment Different permissions per log file when using rsyslog
So simple! Tested, it works. Thanks!
Jul
9
comment How do home routers offer DNS services
I just typed "at" in the comment instead of "@" since @ has other semantics in stack exchange comments. The command issued on the terminal had indeed @.
Jul
9
comment How do home routers offer DNS services
~$ dig at192.168.1.1 www.ntua.gr ; <<>> DiG 9.8.1-P1 <<>> at192.168.1.1 www.ntua.gr ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Jul
9
comment How do home routers offer DNS services
Indeed but on the client machines /etc/resolv.conf has as nameserver the router IP and not IP of external DNS servers.
Jul
9
comment How do home routers offer DNS services
To act either as a DNS cache or a forwarder you need to run a DNS software (bind). The router does not listen to port 53.
Nov
5
comment Git commit auditing
Great idea to use the hook. Will look into it.
Nov
2
comment Git commit auditing
thank you so much for your detailed answer! It really is complete from a systems administrators perspective. What I was looking though was a solution that would not need one to resolve to so much low level auditing, and ideally will prevent forged commits rather than resolve to forensics after the fact.
Nov
2
comment Git commit auditing
Could be either. The current setup is the one described in the question (one ssh account per user), but this does not scale well and I might want to go with single user/many keys in the future. I am just looking for the most versatile solution that will not lock me into one or another authentication method.
Nov
2
comment Git commit auditing
There is still the setup that users login with the same ssh user but use different (authorized) keys. This makes the auditing even harder.
Nov
2
comment Git commit auditing
1. This suggestion seems to be the most apt for my purposes. Still, is there a mechanism to reject unsigned commits on the server side? 2. As far as this solution is concerned the user pulling from the subordinate repo will have to double check that the committer has not used forged username/email. True?