Zero Wine Tryouts – An open source malware analysis tool

Zero Wine Tryouts is an open source malware analysis tool. Just upload your suspicious file (e.g. Windows executable file, PDF file) through the web interface and let it analyze

Download Right Here | More informatian about : Zero Wine Tryouts

TCP/UDP footprint analysis Beta

Providing users the ability to with accuracy map all inbound and outbound TCP/UDP connections to a Process ID and process owner. The application will also map a port to various performance metrics like processor and memory utilization.

Features :

  •     Query all inbound and outbound network traffic endpoints with precision [IP/Hostname/Port].
  •     Map each connection to an application [process id].
  •     Map each application or process to a user account [process owner].
  •     Provide a memory and processing footprint per connection.

Read more right here :

Update Hiawatha V-8.3

Our post Before :

Hiawatha is a secure and advanced Web server for Unix. It has been written with security as its main goal. It features a rootjail, the ability to run CGIs under any UID/GID you want, prevention of SQL injection and cross-site scripting, banning of clients who try such exploits, and many other features. These features make Hiawatha an interesting Web server for those who need more security than what the other available Web servers are offering. Hiawatha is also fast and easy to configure.

Release Notes  8.3 23 May 2012 : This release adds reverse proxy functionality.

Download :
Unix/Linux : hiawatha-8.3.tar.gz
Windows :
MacOS :  hiawatha-8.3.dmg
Read more Right here :

Facebook Auto Poker written in Python

Just put in your email and password and your on your way. It will run and loop back poking people until you stop. Also there is no need to install any external libraries, it runs on the ones that come standard in python. Do also note that if you kill and restart the script to many times within a small period of time Facebook will temporarily block logging in with the script.


Download & Read more in here :

DNSCrypt v-0.9.4 – A tool for securing communications between a client and a DNS resolver.

DNSCurve improves the confidentiality and integrity of DNS requests using high-speed high-security elliptic-curve cryptography. Best of all, DNSCurve has very low overhead and adds virtually no latency to queries.

DNSCurve aims at securing the entire chain down to authoritative servers. However, it only works with authoritative servers that explicitly support the protocol. And unfortunately, DNSCurve hasn’t received much adoption yet.

The DNSCrypt protocol is very similar to DNSCurve, but focuses on securing communications between a client and its first-level resolver. While not providing end-to-end security, it protects the local network (which is often the weakest link in the chain) against man-in-the-middle attacks. It also provides some confidentiality to DNS queries.

The DNSCrypt daemon acts as a DNS proxy between a regular client, like a DNS cache or an operating system stub resolver, and a DNSCrypt-aware resolver, like OpenDNS.


The daemon is known to work on recent versions of OSX, OpenBSD, NetBSD, Dragonfly BSD, FreeBSD, Linux, Windows (MingW or Cygwin), and iOS (requires a jailbroken device).


Download the latest version and extract it: 

$ bunzip2 -cd dnscrypt-proxy-*.tar.bz2 | tar xvf –

$ cd dnscrypt-proxy-*

Compile and install it using the standard procedure: 

$ ./configure && make -j2

# make install

Replace -j2 with whatever number of CPU cores you want to use for the compilation process.

Running make -j2 test in the src/libnacl directory is also highly recommended.

On BSD systems, GNU Make should be installed prior to running the ./configure script.

The proxy will be installed as /usr/local/sbin/dnscrypt-proxy by default.

Command-line switches are documented in the dnscrypt-proxy(8) man page.


Having a dedicated system user, with no privileges and with an empty home directory, is highly recommended. For extra security, DNSCrypt will chroot() to this user’s home directory and drop root privileges for this user’s uid as soon as possible.

The easiest way to start the daemon is:

# dnscrypt-proxy –daemonize

The proxy will accept incoming requests on and encrypt/decrypt them from/to OpenDNS resolvers.

Given such a setup, in order to actually start using DNSCrypt, you need to update your /etc/resolv.conf file and replace your current set of resolvers with:


Other common command-line switches include:

–daemonize in order to run the server as a background process.

–local-address= in order to locally bind a different IP address than
–local-port= to change the local port to listen to.
–logfile= in order to write log data to a dedicated file. By default, logs are sent to stdout if the server is running in foreground, and to syslog if it is running in background.
–max-active-requests= to set the maximum number of active requests. The default value is 250.
–pid-file= in order to store the PID number to a file.
–user= in order to chroot()/drop privileges.

DNSCrypt comes pre-configured for OpenDNS, although the –resolver-address=, –provider-name= and –provider-key= can be specified in order to change the default settings.

Using DNSCrypt in combination with a DNS cache 

The DNSCrypt proxy is not a DNS cache. This means that incoming queries will not be cached and every single query will require a round-trip to the upstream resolver.

For optimal performance, the recommended way of running DNSCrypt is to run it as a forwarder for a local DNS cache, like unbound.

Both can safely run on the same machine as long as they are listening to different IP addresses (preferred) or different ports.

If your DNS cache is unbound, all you need is to edit the unbound.conf file and add the following lines at the end of the server section:

do-not-query-localhost: no


name: “.”



The first line is not required if you are using different IP addresses instead of different ports.


Then start dnscrypt-proxy, telling it to use a specific port (40, in this example):


# dnscrypt-proxy –local-port=40 –daemonize

Queries using nonstandard ports / over TCP

Some routers and firewalls can block outgoing DNS queries or transparently redirect them to their own resolver. This especially happens on public Wifi hotspots, such as coffee shops.

As a workaround, the port number can be changed using the –resolver-port= option. For example, OpenDNS servers reply to queries sent to ports 53, 443 and 5353.

In addition, the DNSCrypt proxy can force outgoing queries to be sent over TCP. For example, TCP port 443, which is commonly used for communication over HTTPS, may not be filtered.

The –tcp-only command-line switch forces this behavior. When an incoming query is received, the daemon immediately replies with a “response truncated” message, forcing the client to retry over TCP. The daemon then encrypts and signs the query and forwards it over TCP to the resolver.

TCP is slower than UDP, and this workaround should never be used except when bypassing a filter is actually required. Moreover, multiple queries over a single TCP connections aren’t supported yet.
EDNS payload size

DNS packets sent over UDP have been historically limited to 512 bytes, which is usually fine for queries, but sometimes a bit short for replies.

Most modern authoritative servers, resolvers and stub resolvers support the Extension Mechanism for DNS (EDNS) that, among other things, allows a client to specify how large a reply over UDP can be.

Unfortunately, this feature is disabled by default on a lot of operating systems. It has to be explicitly enabled, for example by adding options edns0 to the /etc/resolv.conf file on most Unix-like operating systems.

dnscrypt-proxy can transparently rewrite outgoing packets before signing and encrypting them, in order to add the EDNS0 mechanism. By default, a conservative payload size of 1280 bytes is advertised.

This size can be made larger by starting the proxy with the –edns-payload-size= command-line switch. Values up to 4096 are usually safe.

A value below or equal to 512 will disable this mechanism, unless a client sends a packet with an OPT section providing a payload size.
GUIs for dnscrypt-proxy

If you need a simple graphical user interface in order to start/stop the proxy and change your DNS settings, check out the following projects:

DNSCrypt OSX Client: a preferences pane, a menu bar indicator and a service to change the DNS settings. OSX only, written in Objective C. 64-bit CPU required. Experimental.

DNSCrypt WinClient: Easily enable/disable DNSCrypt on multiple adapters. Windows only, written in .NET.

DNSCrypt Win Client: Official GUI for Windows, by OpenDNS.

Download Version :
Windows :
Unix/Linux : dnscrypt-proxy-0.9.4.tar.gz
iPhone : dnscrypt-proxy-iphone-0.9.4.tar.gz.sig
Find Other Version |
Read more in here :

EPG – Extended Password Generator V2.0 released

EPG – Extended Password Generator is an unique tool which can help you to generate pronounceable and random passwords, secure against brute-force dictionary attacks.

Recen releasead Changes in 2.0: – Implemented checking user’s provided passwords – No more MFC, 100% written with ATL/WTL (including Grid, Clipboard, printing, etc) – Visual Studio 2010 – WTL 8.1 – Boost 1.49

This algorithm was initially suggested by National Technical Information Service (NTIS), developed at Federal Information Processing Standard (FIPS) No181 “Automated Password Generator” and modified by me to implement exclude/include scheme

Platform : Windows
Download :
Read more in here :

Mandragora Linux Beta Released

Mandragora Linux – A hardened Linux desktop for use in Digital Forensics-Incident Response (DFIR) and Vulnerability Assessments. Mandragora leverages AppArmor security profiles and auditing, LXC Container Sandboxing (Arkose) and Tor and I2P for enhanced privacy. Mandragora is built upon Ubuntu 12.04 LTS and uses the GNOME3 Classic desktop environment.
Download : Mandragora.ova (2.7 GB)
Read More In here :