Free vnc spy 0.1 software for linux

VNC Spy monitors network traffic to find keystrokes entered into a VNC viewer. Letters the user types are printed to your screen.

So, for example, if an engineer insists on using VNC to log in from his Windows machine into your network whenever he wants from home, try leaving vncspy running for a while. I like to use the command:

sudo vncspy eth0 | tee keylog

Note that you need to run vncspy as root. You can either su root, or sudo.

This will sniff all keystrokes he enters from home to his VNC server. Assuming he has to enter his user name and password to log-on, you should see his user name in the keylog, followed by his password. Its that simple!

When you get his password, try writing it on a sticky-note, and pasting it on his monitor. Ive found showing people their passwords to be very effective at improving their security habits.

Usage:

vncspy must be run as root. It takes only one optional parameter, the interface to sniff on. If left out, it will use the first interface on your system, typically eth0.

Compling:

The only major dependency for vncspy is the pcap development library. On Debian or Ubuntu, you may issue a command like:

sudo apt-get install libpcap0.8-dev

If your system does not have libpcap available, you can install it from source from:

http://www.tcpdump.org.

Once you have libpcap, compiling vncspy is simple. Just type:

make

It should create the vncspy program. Let me know if you need help.

TkVNC is a VNC viewer written in pure Tcl/Tk. It does not yet support authentication, so it can only connect to an unsecured VNC server. All the original "classic" encodings are supported. It was written to be embedded inside another application, however the version here is a standalone program.

Current status (9 Jan 2003).
DES encryption (i.e. authentication) is not implemented. Therefore, you cant connect to something that was started with Unix vncserver, only Unix Xvnc -rfbport ... directly would work
Tested against TightVNCs Xvnc and OSXVncs OSXvnc-server
raw encoding works
I havent seen a server using copyrect, so I dont know if that works
hextile is still a little confused and very slow (often kills Xvnc?) There seems to be a CPU leak in the Tk image command.
RRE is implemented, but I think Xvnc doesnt give sensible results
CoRRE is implemented, also gets strange results from tightvncs server
tight and zlib encodings are not implemented
no support for SetColourMapEntries
no support for ClientCutText (but ServerCutText is OK)
Big-endian-ness is hard coded. This is obviously a bit of a problem on x86 platforms!

To test it just do the following:
Xvnc :1 -geometry 800x600 -depth 8 &
twm -display :1 &
xterm -display :1 &
And on the client (which is any platform with Tk):
wish tkvnc.tcl ?server:1?

vnc2swf is a recording tool for VNC that records sessions and generates a Macromedia Flash movie file (SWF).

The project can be used as an X11 recorder or a Windows desktop recorder.

LibVNCServer is a library that makes it easy to make a VNC server. All you do is provide a frame buffer and some I/O functions, and call a function each time the frame buffer changes. It supports all encodings known, including tight, zlib, ZRLE, and cursor encodings.
LibVNCServer also includes the HTTP server from Xvnc, so you can start a java viewer by surfing to http://my.vnc.server:5801 or similar. It includes a beta version of LibVNCClient, which makes it easy to make a VNC client. Also included is LinuxVNC, which is to the Linux console as WinVNC is to the Windows desktop.
If you dont know VNC, have a look at the original VNC or at Tridia VNC, who also have commercial support for it.
Now that you know what it is, maybe you want to make your own server. If this is not the case, you can ignore the rest of this page an go on surfing the internet.
Now that you want to make a VNC server, that is, a server which speaks the RFB protocol, you can download this library from sourceforge.
The simplest server looks like this:
#include
int main(int argc,char** argv)
{
rfbScreenInfoPtr server=rfbGetScreen(&argc,argv,400,300,8,3,4);
server->frameBuffer=malloc(400*300*4);
rfbInitServer(server);
rfbRunEventLoop(server,-1,FALSE);
return(0);
}
This sample creates a 400x300 frame buffer in true colour. There are 4 bytes per pixel, because 3 (which are only used instead of all 4) is such an odd number. Then the server is initialized and a blocking event loop is started.
Of course, this program only shows rubbish (whatever is in the frame buffer you mallocd), but it proves that writing a server can be very easy.
For details (especially if you want to write a real server) look into the provided examples, pnmshow.c and example.c, and into the README. You find there documentation for much more complicated servers.
Enhancements:
- The x11vnc source code is no longer included in the package.

Craftsman Spy is a an open source and free framework for JDBC logging. Craftsman Spy is a JDBC driver implementation.

This logger logs all SQL connection and processings with execution spent time, all the stored procedures with arguments, all the batch processings and the result sets.

No need to modify your application in order to integrate JDBC logging with Craftsman Spy. The application MUST use the craftsman.spy.SpyDriver and MUST be launched with the -Dspy.driver=... system property.

Be carefull this JDBC driver SHOULD not be used in production mode. Use it only in development or pre-production system.

,b>Usage:

Code

The two solutions can be used as the following examples :
System.setProperty("spy.driver","vendor.database.Driver");// or with the -Dspy.driver=vendor.database.Driver JVM option
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:database:mydata");
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:spy:vendor.database.Driver:database:mydata");

Log configuration

The log4j.properties or log4j.xml configuration file SHOULD contain the following lines :
log4j.category.craftsman.spy=DEBUG, SpyFile
log4j.appender.SpyFile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.SpyFile.DatePattern=.yyyy.MM.dd
log4j.appender.SpyFile.File=spy.log
log4j.appender.SpyFile.layout=org.apache.log4j.PatternLayout
log4j.appender.SpyFile.layout.ConversionPattern=%m%n

x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way x11vnc plays the role for Unix/X11 that WinVNC plays for Windows.
I wrote x11vnc because x0rfbserver was basically impossible to build on Solaris and had poor performance. The primary x0rfbserver build problems centered around esoteric C++ toolkits. x11vnc is written in plain C and uses only standard libraries. I also added a few enhancements to improve the interactive response, add esoteric features, etc.
For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a physical display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop.
The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol (the exception is cached pixmap data on the viewing-end). Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
Enhancements:
- A compile-time bug is fixed for when the OpenSSL library is not available or --without-ssl is supplied; previously the build would fail.
- One can configure x11vnc via "configure --with-system-libvncserver" to use a system installed libvncserver library instead of the one bundled in the release tarball.
- If UltraVNC file transfer or chat is detected, then VNC clients are "pinged" more often to prevent these side channels from becoming serviced too infrequently.
- In -unixpw mode in the username and password dialog no text will be echoed if the first character sent is "Escape". This enables a convenience feature in SSVNC to send the username and password automatically.
Miscellaneous new features and changes:
- When building from the CVS tree --with-x11vnc must be supplied if you want x11vnc to be built. The LibVNCServer release tarball no longer contains the x11vnc source.

SDL_vnc library was created to offer a VNC client system that:

- is LGPL licensed and can be used in commercial applications
- integrates with SDL (framebuffer is a SDL surface)
- IO and processing runs as a thread, so it does not interfere with a traditional "game loop"

Supported Platforms:

The library compiles and is tested on a Linux target with a TightVNC server running on windows.

Installation and Test

To compile the library your need the SDL 1.2 installed from source or installed with the devel RPM package. For example on Mandrake, run:

urpmi libSDL1.2-devel

The run

./autogen.sh (optional)
./configure
make
make install
ldconfig

to compile and install the library. The default location for the installation is /usr/local/lib and /usr/local/include. The libary path /usr/local/lib might need to be added to the file /etc/ld.so.conf

Then run ldconfig again.

VNCcrack is a simple, fast offline-mode VNC password cracker. VNCcrack takes a set of challenge-response pairs of the type passed during a VNC authentication attempt, and attempts to recover the passwords using a dictionary file.

Usage: ./vnccrack wordlist crpairs