Make Site Changes Easier by Editing within phpMyAdmin

Posted at August 23, 2014 at 9:18 am by admin

Many people use CMS systems such as WordPress, which store data in sql tables within a database. This is also true of ecommerce solutions which consist of WordPress plugins, and for other systems such as Joomla and Magenta. If you have a store which is part of a blog site then typically the data for an ecommerce plugin will be in a separate database from that which contains the blog.

There are a number of problems that can be eliminated by editing data directly in the database using phpMyAdmin.

1)   You can add information even when it won’t normally ‘stick’. Read More

Open DNS Resolver – The Threat it Poses and Remedies to Prevent Exploitation

Posted at July 28, 2014 at 7:00 am by admin

An Open DNS Resolver is a DNS server that’s willing to resolve recursive DNS lookups for anyone on the internet.

DNS resolvers that allow requests from all IP addresses and are exposed to the internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the abuser. That means you become a silent facilitator for a large scale attack. DNS amplification attack is a popular form of Distributed Denial of Service (DDoS).

The primary technique consists of an attacker sending a DNS name lookup request to an open DNS server. Read More

OpenSSL Security Bug

Posted at April 8, 2014 at 7:20 pm by admin

OpenSSL exploit and vulnerability has recently been discovered.  It is highly recommended that servers running the vulnerable version of OpenSSL (1.0.1 and 1.0.2beta) are upgraded immediately.



https://www.openssl.org/news/secadv_20140407.txt


OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160)
==========================================

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including
1.0.1f and 1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to
Adam Langley <agl@chromium.org>
 Read More