Archiwum kategorii: security

node.js security slides from SEConference 2014

node-js

Yesterday I gave talk about node.js security during SEConference here in Kraków. It was fun – especially afterparty where we could do some nerd – talking about our security concerns :)

Oh and that part:

me: “- hey, where did you get this Dragon Sector t-shirt?”

vnd: “- because I’m the member of Dragon sector”

me: “- LOL, that explains everything”

And I was wondering why this guy is called “vnd” – just like that one from Dragon Sector. It was so obvious – lolme ;)

Ok so now – slides:

Node.js security from Maciej Lasyk

Moving WordPress admin panel to another TCP port (with SSL)

  • Wordpress logoLast time I’ve been working on my WordPress installation security. I added a few layers of high-level-security-paranoia. One of those was moving admin-panel to another TCP port (this was because I got only 1 public IP addr on this VPS and that means only one SSL legit certificate on 443 port. So – each SSL webservice on my server is now binded to a different TCP port and those are ‘SSL green’ ;) ).

    Running admin panel over SSL is a thing which has already been described on a many websites:

    But I haven’t found any article about running Admin Panel over SSL on different port than the website. So I took a deep dive (oh not that deep) into WordPress code and found, that it’s really that simple ;) Assuming my admin panel is running on TCP/445 port and website is as usual on TCP/80 all i had to do was this chunk of PHP code (maybe not that clean, but it’s just working fine) – put it in wp-config.php file:

    References:

SELinux && Ganglia / Multicast && Apache && RRDs

SELinuxWhile setting up test server with Ganglia triad (gmetad, gmond, gweb over Apache) I had only 2 SELinux alerts to solve. First one regarding to denial of /var/lib/ganglia/rrd access by httpd process (while accessing ganglia-web interface):

In order to resolve that I just added SELinux contexts to rrdtool binary and /var/lib/ganglia/rrds dir:

The last SELinux alert was regarding to Apache trying to access port 8652 by socket connection (on ganglia-web I saw error like “fsockopen 8652 access denied”):

So I had to create local policy for this particular occasion as there is no ganglia modules for SELinux (maybe I should create one…?). Firstly let’s check that there’s no even one module:

So let’s create this policy:

After this everything should work like a charm. To confirm that We have this new policy working: