You may be required – for example by PCI compliance – to update your SSH server to plug some vulnerabilities that some dumb scanner has flagged. The fact is alot of these vulnerabilities are probably already patched as part of OS updates, but you may be required to do it for some other reason.
If you’re using Java configuration (i.e. not XML) and are using endpoints that have a “.” in the last token of the path you’ll probably have noticed the default Spring behaviour where anything after the “.” is truncated.
Luckily there’s a simple fix.
You will often come across the case where you have your main MongoDB database for your application, and then require some other database (perhaps on an entirely different server). Luckily Spring JPA / MongoDB integration is incredibly flexible and it’s a fairly straightforward process.
In the example below I use class-defined configuration/beans rather than XML files.
The documentation on the MongoDB is pretty intense. When you’re starting out, all you want to do is create some super user and then some other user that uses the database to insert/read documents.
So here’s how…
A short update on installing MongoDB on 16.04 [LTS] as the documentation on the MongoDB site is slightly incorrect.
So you’ve inherited a project – from git or wherever – and you want to start looking at the code. You might not have a mac, and even if you do you might not have all the tools you need on the machine to be able to start looking at the code and debugging it…
Continue reading Xcode: [Very]Quick Start for Existing Projects
A common(ish) error with a common cause.
Continue reading quickfix.Session – [FIX/Session] Disconnecting: Encountered END_OF_STREAM
(Valid for Ubuntu 14.04 – I suspect its the same for the latest versions)
I struggled a bit with getting SSL working simultaneously disabling port 80, i.e. redirecting anything attempting to get to http://mysite.com to https://mysite.com. In the end it was actually super easy, here’s how I did it.
You often don’t want your web root directory to be in the default place for Apache2. It’s fairly easy to switch it.
Pretty quick one, and dead useful (though you’ll want to be careful about where you place your web directory so as to not cause a security hole).
It shouldn’t be that hard to spot new TCP/UDP connections to your API or database server. Of course there’s dozens of tools to help you do this but here’s two gems I use regularly to quickly figure out who’s connecting to my servers.
devpolito 