Using squid to cache FreeBSD packages
PKGNG config
I manage a few FreeBSD jails behind a squid proxy. pkgng is configured to use the proxy:
Read more...I manage a few FreeBSD jails behind a squid proxy. pkgng is configured to use the proxy:
Read more...I purchased a Yubi NEO I’ll use it to hold my Luks password and for ssh authentication instead of the password authentication that I still use.
You’ll find my journey to get the smartcard interface working with ssh on a fedora 22 system below;
Read more...I’m creating a new openvas 7 system running centos 7 as a KVM instance.
The installation went fine but it was impossible to create new credentials.
I had a similar issue with my openvas 6 installation, this was resolved by creating the /etc/openvas/gnupg
directory and creating the key openvasmd --create-credentials-encryption-key
But on my openvas 7 installation a creation of the encryption key was slooooow. As always Good Randomness is important for creating keys. So I decided to install haveged to get more randomness and hopefully this would speed up key creation.
[root@localhost ~]# yum install haveged
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* atomic: www6.atomicorp.com
* base: centos.cu.be
* extras: centos.cu.be
* updates: centos.cu.be
Package haveged-1.9.1-2.el7.art.x86_64 already installed and latest version
Nothing to do
[root@localhost ~]#
[root@localhost ~]# systemct list-unit-files --type=service | grep haveged
-bash: systemct: command not found
[root@localhost ~]# systemctl list-unit-files --type=service | grep haveged
haveged.service disabled
[root@localhost ~]# systemctl enable haveged
ln -s '/usr/lib/systemd/system/haveged.service' '/etc/systemd/system/multi-user.target.wants/haveged.service'
[root@localhost ~]# systemctl start haveged
[root@localhost ~]#
The key creation took a only sec.
[root@localhost ~]# openvasmd --create-credentials-encryption-key
Key creation succeeded.
[root@localhost ~]#
Adding new credentials works like a charm now.
Happy hacking!
Read more...Update (Mon Jun 8 2015): Running google-chrome inside a docker container isn't stable for me. I switched back to LXC to run google-chrome which seems to be more stable.
Created a docker image to start a docker container with chrome. Destroying the container each time that you start a browser is a easy way to get rid of your cookies and browser history.
Read more...Happy new year!
Read more...