i’ve ‘convinced’ my samba running under debian wheezy/jessie to provide me access audit logs without being too verbose. here’s how.
i’ve done a routine upgrade of wordpress 4.1.x to 4.2 and later 4.2.1. all seemed fine until the day i wanted to manually adjust the menu structure using wp-admin > appearance > menus. each attempt of saving my menu resulted in it being wiped out completely
one day an openvpn that used to carry traffic for the last 7 years started to misbehave. openvpn’s own built in watchdog was restarting it every few minutes. one of the tunnels endpoints – a- is behind NAT that we don’t control, another – b – is a host with public ip address.
we still have bunch of servers with DRAC5 cards. after upgrade to java 8u31 java-based kvm console stopped working. it gives: “error when reading from SSL socket connection.” message box during startup and that’s it.
the idea: i’d like to run kvm/lxc on debian, have guests bridged to couple of vlans and handle the network failover on the host level. network failure should be detected using arp probes not just the link [ mii ] status. after few attempts i got it working in the test environment.
http://sitecheck.sucuri.net/ for checking if a live website is referring to some malicious js / having unwanted iframes https://www.rfxn.com/projects/linux-malware-detect/ and http://www.clamav.net/index.html and http://www.eset.com/ for scanning files for unwanted conten from the command line:
i’ve received for testing a new dell r630. before buying few of those i wanted to make sure that debian wheezy has kernel including all the needed drivers. it seems that it has.
docker seems to be the new fad… which i don’t use at all; but i’m quite happy with lxc and have it deployed in the production on couple of servers.
it’s high time to move away from truecrypt [ which i’m doing by moving to luks and btrfs on the top of it for extra thrills ], but i still have bunch of places that were not moved to the alternative full disk encryption. what do do when after unclean shutdown this happens: ?
sometimes after few lan failovers linux decides to use different bonding slave than i’d like it to. solution – remove from the bond interface acting as undesired master and then re-add it: … and nagios stops nagging.