Looks like I’m running low on disk on my virtual machine (VM) running ownCloud. Luckily, there’s plenty more available on the host so today I’m expanding the logical volume (LV).
Step one – as always, BACKUP your data. I use rsnapshot together with ssh and mysqldump.
Step two – shutdown the guest.
Step three – On host run (as root): ssm resize /dev/vg0/cloudStorage -s+250G. Where vg0 is the name of your storage pool and cloudStorage is the name of your LV. SSM is a smart tool that takes care of partitioning, logical volumes, storage pools and file system.
Step four – Start your guest: virsh start ownCloud (or whatever the name of your VM).
Done. Happy clouding!
A week or so ago, ownCloud 8 was released as the next stable version. Some new features include a better administration view, ability to flag files as favorite and a new search engine that filters the current view first, followed by searching your repository. I will upgrade my own instance and post the upgrade notes here at a later time.
In my quest to increase security on a few servers I run that are facing the Internet, I’ve started to utilize private/public key authentication and limit which IP’s that can connect via SSH. The priv/pubkey is not new to me, in fact I’ve used it for the past ten or so years. Only that the certificate I’ve used for that time is very weak. So figured I’d do something. And I also do not like typing passwords all the time, but I want a pass phrase on my certificate. Insert SSH Agent!
Essentially, SSH Agent loads your private key, you type in the password once and then it remembers if for you. And it can be forwarded to the next server to chain it all together nicely.
I won’t do an overly detailed to-do this time, but essentially here’s what I did:
- Build a new certificate pair: ssh-keygen -b 4096 -t rsa -C MyKey. You will be asked to enter a password, which is recommended. In ~/.ssh you’ll find id_rsa and id_rsa.pub.
- Copy the contents of id_rsa.pub into your server’s ~/.ssh/authorized_keys. One key per line if there are multiple ones.
- Try the connection: ssh -o PasswordAuthentication=no you@yourserver. This should force the use of the keys. If all works well, you’ll get to enter the password OF YOUR KEY, not the account password. Then connect.
- All good? Then let’s start agent (this is preferably done in ~/.bash_profile): eval `ssh-agent`. Followed by ssh-add. You can specify which key(s) to load here, but that’s for another time. Try step #3 again, and you should pop right in, no questions asked.
- Good! Then let’s disable password authentication. Edit /etc/ssh/sshd_config and find PasswordAuthentication. In some cases it explicitly says “PasswordAuthentication yes”, in others it’s commented out because it’s the default. We want to uncomment this and set to NO. So: PasswordAuthentication no.
- Now restart SSHd, by sending “killall -HUP sshd“. There are other elegant ways to do this, but it does the trick. If your key does not let you in now, then you’re in trouble… Don’t blame me. :)
- Optional: In addition to this, I opt to only trust IP’s that I know. So I added this to /etc/hosts.deny: sshd: ALL and to /etc/hosts.allow; sshd: [2001:123:456:789a::]/64. This makes sure that only my IPv6 range can get in. The changes to hosts.allow and hosts.deny takes immediate effect, so be careful.
- Should be pretty safe now :)
If you’re on a Windows client and use PuTTY, there are tools for this too. Use PuTTYgen to create or convert the keypair, and Pageant as the running agent. PuTTY and WinSCP will use Pageant when you try to connect, by default.
With more and more integrity issues floating to the surface, and privacy becoming more of a focus, I’ve started to look into what I can do.
For one, I’m trying out DuckDuckGo as a search engine instead of Google. Their philosophy is to not track people, making the web a tiny bit more anonymous. I’m happy enough with the search results, can’t really say I miss anything that Google found for me.
The other is that I’m starting to secure websites I’m working on with HTTPS. This is really way overdue for everyone, and HTTP/2 being on the work bench it’s about time that we all pick ourselves up and encrypt website traffic. It should be for the viewer’s eyes only. SSL certificates can cost a few bucks, and there are options from around $5 around the web, to the free option at StartSSL.com, which only really requires you to verify that you run the domain you claim the certificate for. Excellent service, and quick! I can highly recommend.
I’ve just released my PHP site library easily named SiteFramwork on GitHub. I just needed to bring my libraries together and find a way to share it between my various projects. Git and GitHub turns out to be a pretty good choice.
Take a peek, and let me know your thoughts: https://github.com/SimFre/SiteFramework