Angel and I made a date to look for her shoes that she will wear to a garden wedding this weekend. We decided to go to Podium since I was also planning to buy a new pair of Espadrilles from Sueño de Espadrilles. I originally own a dirty white pair but because I had it washed, it became beige and are choking my feet [they shrunk!]. **Note: Espadrilles are not meant to be washed.

Espadrilles by Sueño de Espadrilles

Aside from Podium, I planned to do my errands today since Blade Mall of Asia has long been texting me that the seat cover I ordered was finally in the store. So I finally did get the seat cover and fetched Angel at Glorietta.

When we got to Podium, we were so hungry that we decided to eat lunch first, hence Kimono Ken. Normally, when I eat in Japanese restaurants, I order Teriyaki Chicken or Teriyaki Salmon. But this time, I decided to go for a change and tried a new dish [will supply this name later on]. It was soooo goooood and it only cost me P150! Change is good.

After eating, we went shoe hunting. And boy! Did we find some shoes!

Even though I was planning to buy my Espadrilles, I was unable to because they did not have the style I wanted. On the other hand, I found this adorable baby that blew me away. Instead of getting the Steve Madden shoe which would cost me close to P9000, I am getting this shoe instead.

Bootie by Substance

I was really about to pay for it but the saleslady could not give me a discount [there's a defect on the back]. So anyway, she reserved the shoe for me until she confirms with her boss.

Angel, meanwhile, was able to buy whore heels from People are People [picture next time] which only cost her P600! They were so cuttteee!! But she later realized that she still needed shoes for the wedding. Since she was running low on money, we both decided to look for shoes which would only cost P400.

So after Podium, we went to Galleria since I had a schedule to visit Gold’s Gym. While I checked out the amenities of the gym [planning to join? get in touch with me! They have a promo!!!], Angel checked out the shoes in the Department Store.

When I was able to catch up with her, I told her VNC was having a sale and we should check out 50th Avenue as well. So we did, and finally, Angel found shoes from Cole Vintage at only P300! Meanwhile, I found another new pair of shoes to drool over from VNC. They still cost P2,600+ and they’re breaking my heart..

Pod Debianem łatwo możemy dostać się na któryś z pulpitów w sieci LAN. U mnie potrzeba ta zrodziła się z kilku powodów:

• mam mały komputerek dell gx150
• na laptopie nie chcę instalować drugiego menedżera okien
• chcę przetestować lxde
• mam uszkodzony monitor

O zaletach i wadach nie będę się tutaj rozwodził. Przedstawię bardzo łatwy sposób jak uzyskać zdalny pulpit.. do rzeczy…

Serwer

Serwer będzie określał komputer z którego będziemy “pobierali” pulpit na inny komputer w sieci. W tym celu należy zainstalować odpowiednią paczkę, ja korzystam z x11vnc, instalacja wygląda tak:

aptitude install x11vnc

O tyle mamy łatwo, że pakiet ten po zainstalowaniu nie wymaga żadnej konfiguracji, powinien ruszyć od razu.

Należy jeszcze sprawdzić czy firewall nie blokuje portu po którym będziemy się łączyć, np. 5900. Otwieramy go dopisując do naszego firewalla:

iptables -A INPUT -p tcp –dport 5900 -j ACCEPT

Możemy już uruchomić nasz serwer:

x11vnc

Jeśli nie wyrzuca żadnych niepokojących komunikatów to wszystko okay, jeśli jest inaczej czytamy co mu się nie podoba…

Klient

Po stronie klienta, czyli tutaj skąd będziemy się łączyli na zdalny pulpit instalujemy klienta vncviewer:

aptitude install vncviewer

Do podstawowego działania również nie wymaga konfiguracji podobnie jak pakiet odpowiedzialny za serwer połączenia. Jeśli mamy uruchomiony serwer to możemy już teraz podjąć próbę połączenia się z nim:

vncviewer 192.168.1.24::5900

- 192.168.1.24 — adres hosta
- 5900 — numer portu po którym się łączymy

Efekt:

Following up my earlier post about recording a VNC session to a screencast, I’m pleased to have a first attempt to show you:

This is a basic ‘tour’ of my 701’s desktop, which is now running the Fluxbox window manager. The movie is mostly a test to see if the ’setup’ would work—in future, I’ll ’script’ the thing before I make it!—but I reckon I can use this method for other ‘proper’ screencasts.

To capture the Eee desktop, I ran the “krfb” desktop-sharing app on the 701, which uses the VNC protocol to allow remote access to the Eee’s display. The actual capturing was done using ScreenToaster, a fine example of how advanced Web-based applications have become at the end of the 2000s.

ScreenToaster allows you to record a commentary using any microphone on your computer, and apparently it can even use your webcam if you have one, though I have yet to test that. As long as you have a computer with Java and a reasonable amount of CPU power, I think ScreenToaster does the job as well as (and possibly better than) your typical lower-range shareware screen-capture program, and is worth a look if you need to capture a screencast.

Ironically, one advertised ScreenToaster feature which I was hoping to use—the ability to record the output of a VNC session—didn’t work for me at all (it tried to overlay the 800×480 VNC display over our iMac’s 1600×1250 (?) screen, and capture that). Therefore, to make this screencast, I had to bring up the Eee’s VNC display on the Mac, and tell ScreenToaster to capture the part of the Mac’s desktop which was showing the VNC display. A bit of a “hack” (and this may have been why there are two mouse pointers sometimes!), but at least it worked!

Finally, I exported the movie from ScreenToaster as a QuickTime (MOV) file, and did some editing in iMovie 08, as well as adding captions, the “Digital Ramyun” opening and closing titles, credits, etc.

So, perhaps this isn’t the most thrilling viewing (OK, it isn’t ), but as a “proof of concept” I think it does the job…

Steps in nut shell

For RHEL4
——————
up2date @”KDE (K Desktop Environment)”
up2date vncserver
——————

For RHEL5 or Centos
——————
yum groupinstall “KDE (K Desktop Environment)”
yum install vncserver
——————

Edit the lines below in the file /etc/sysconfig/vncservers and add a user “test” (user should be a valid user created on your server and not just simply a name).
——————
VNCSERVERS=”1:test”
VNCSERVERARGS[1]=”-geometry 1024×768 -depth 16″
——————

Add a password
——————
$ vncpasswd
Password:
Verify:
——————

Edit the startup script
———————-
$ vi ~/.vnc/xstartup

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
———————-

Go for Reboot…….(for KDE installation to take effect)

When the server is back
Type the command below to start the VNC server.
———————-
$ vncserver :1
———————-

Test whether the port is listening.
———————-
telnet localhost 5901
———————-

Open up the port 5901 in your Firewall settings.

From your local machine telnet to the VNC port

———————-
telnet IP 5901
———————-

The server is now ready to serve the request.

Connect to VNC server from your local machine.
Allow 5901 in your firewall (local machine)

Now from the console type

—————————
vncviewer IP:5901
It will ask for you login
—————————
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

How To install VNCserver?

This part is to be done with the server.

Usually Linux servers are not installed with graphical interface(only text mode).
However, for VNC to gain access of the userfriendly interface like windows, KDE (K desktop environment) is installed.

Installation of KDE or GNOME

===========================

RHEL4
up2date @”KDE (K Desktop Environment)”

RHEL5 or Centos
yum groupinstall “KDE (K Desktop Environment)”

===========================

Reboot is required for this to take effect.
We will go for reboot after the complete installation.

VNC server

===========================
RHEL4
up2date vncserver

RHEL5 or Centos
yum install vncserver
===========================

The installation is over.

Next part is to configure VNC.

===========================
Add a user(s)

Next we need to add at least 1 VNC user, open the file /etc/sysconfig/vncservers as root and add the information

——————
VNCSERVERS=”1:test”
VNCSERVERARGS[1]=”-geometry 1024×768 -depth 16″
——————

VNCSERVERS=”1:test”, this sets up a users for the vnc server, you can add as many as you like here. The VNCSERVERARGS[1] line refers to the arguments for user 1, in this case the only user (user should be a valid user created on your server and not just simply a name).

Geometry sets the size and depth sets the colour depth
Assuming the client machine has a resolution of 1024×768 and the depth 16

The Port number is obtained 5900 + usernumber.
Here the port number is 5901

If, for example I have 20 users to access the server.
The user 10 will be connecting to port 5900+10

The user should in /etc/sysconfig/vncservers as

VNCSERVERS=”10:newone”
VNCSERVERARGS[10]=”-geometry 1024×768 -depth 16″

Setting password for vncserver

Add a password that must be given before a connection can be established, open a terminal and type:

——————
$ vncpasswd
Password:
Verify:
——————

Edit some startup options and start the server

To start the server we type the command ‘vncserver’ and the session you wish to start (if you have set up more than 1 entry in the
/etc/sysconfig/vncservers file:

$ vncserver :1

To start 10th user

$ vncserver :10

The part below will be shown up.

+++++++++++++++++++++++++
Starting VNC server: 1:test
New ‘linux.test:1 (test)’ desktop is linux.test:1

Starting applications specified in /home/test/.vnc/xstartup
Log file is /home/test/.vnc/linux.test:1.log
+++++++++++++++++++++++++

Next, we need to edit the startup script in the .vnc folder in your home directory.

———————-
$ vi ~/.vnc/xstartup

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
———————-

Next we need to restart vncserver to pick up the change we just made.
To restart the vncserver we need to kill the process and start a new one as root

———————-
$ vncserver -kill :1
Killing Xvnc process ID 15562
———————-

Go for Reboot.

Type the command below to start the VNC server.

———————-
$ vncserver :1
———————-

Test whether the port is listening.

———————
telnet localhost 5901
———————-

Open up the port 5901 in your Firewall settings.

From your local machine telnet to the VNC port

———————-
telnet IP 5901

———————-

The server is now ready to serve the request.

Connect to VNC server.

If your local machine is running Linux (Fedora).

—————————
First we should allow port access 5901(VNC port).
Allow 5901 in your firewall (local machine)

Now from the console type

vncviewer IP:5901
It will ask for you login

You need to install the VNC viewer in your local machine.

If your local machine is running Windows, then please use the link to install the VNC client.

http://www.internetfixes.com/remote_setup/vnc_install.htm

Amongst the features I’m hoping to add to this blog, are ’screencasts’ (“desktop movies”, or “animated screenshots”) made with my Eee 701, to demonstrate how to perform certain actions, show off applications, and so on.

I’m looking at various ways to achieve this, and the method I’d prefer is to run a VNC server on the Eee (probably using the “krfb” screen-sharing app, which I understand is based on VNC), then connect to this from our Mac and record the output, if possible adding an audio commentary as I go along.

However, I’m writing this post mainly to ask: does anyone know of a Mac application which can record screencast movies from a remote VNC session, and do so with a nice easy-to-use GUI?

I’ve searched quite extensively for such an app, and to date have only found two which come even close. The first is vnc2flv, a cross-platform program which can capture a VNC session to an FLV (Flash movie) file. This program is available for Linux and Mac, and comes with a script which can combine the movie-recording with a simultaneous audio track.

Whilst vnc2flv would certainly do the job (and may have to), it’s console- instead of GUI-based, and looks as if it could become quite fiddly, particularly if using the script to record an audio commentary simultaneously. As a result, I wondered if there was a more “polished” Mac application with the same features (and hopefully more).

The only other candidate I’ve found so far is ScreenToaster, a screencasting app which can capture output from a VNC session. I’ve yet to try it, but apparently it runs on Macs, it can record the output of a VNC session, and it’s free.

What’s not to like? I don’t know yet, but on the face of things: it’s Java-based; the movies are Web-hosted, so I don’t yet know if/how easily I can export them; and I have to see if it can work within a home LAN.

I’ll come back here and post further details when I have them, but ScreenToaster could turn out the most “polished” screencasting/VNC solution I’ve encountered… or perhaps the only one!

(Updated 27/10/2009, to reflect the fact that I found ScreenToaster as I was writing the article, but didn’t update the earlier section of vnc2flv to reflect this. Oops.)

Altro post del ciclo delle Idee Condivise: in questa occasione trattiamo un argomento che spesso e’ motivo di dibattito all’interno della community, e per cui ancora meno che in altri casi non esiste una risposta giusta a priori.

Il tema e’ quello del supporto agli utenti “domestici”, quelli che installano Linux per curiosita’ o se lo trovano sul proprio PC a seguito di un LIP ma che hanno qualche difficolta’ nel corretto funzionamento del sistema. Credo che il topic non richieda ulteriori spiegazioni: a qualunque linuxaro e’ capitato di avere richieste di assistenza da parte di amici, conoscenti o perfetti sconosciuti, vuoi per far funzionare una data periferica vuoi per configurare un programma. Sia su Linux che su qualunque altra piattaforma, chiaramente, ma per ovvi motivi ci concentriamo qui su problematiche legate al software libero. In linea di massima, e fatte le debite eccezioni, i tecnici linuxofili si distinguono in due categorie: chi e’ disposto a dare una mano immolando un po’ di tempo al prossimo ingegnandosi per risolvere gli altrui impicci, ed i sostenitori della filosofia RTFM, coloro che non solo evitano di prodigarsi in questa pratica ma pure la reputano dannosa a fini pedagogici poiche’ provvedendo sempre una soluzione pronta gli utenti non imparano nulla. Chi pensa di rientrare nel secondo insieme di persone e’ pregato di interrompere la lettura di questo post ed al piu’ tornare nel prossimo futuro, quando per la serie di idee condivise esporro’ qualcosa di piu’ confacente alla linea di pensiero “DIY”: questo giro e’ dedicato a chi si dedica.

Le persone che necessitano di assistenza e supporto sono molte, ancor piu’ da quando l’installazione di Linux e’ divenuta una operazione davvero alla portata di tutti e numerosi sono coloro che nell’intimita’ domestica piazzano sui propri hard disk Ubuntu o Fedora per poi trovarsi arenati nella configurazione di qualche dispositivo o nella comprensione di qualche meccanismo fondamentale per la manutenzione del proprio sistema (il concetto di package manager su Windows o MacOS non esiste, e non e’ immediato da assorbire senza debita spiegazione). Una minima quantita’ di queste persone e’ conscia dell’esistenza di LUG ed altri enti locali di appassionati cui rivolgersi in caso di perplessita’, e di questi solo una parte si preoccupa di informarsi sul calendario di Install Party ed analoghi eventi di scambio. E pure laddove esistesse una rete capillare di comunicazione, comunque gli appuntamenti sarebbero troppo pochi per far fronte a tutte le richieste e statisticamente non sempre in giorni ed orari accessibili a tutti. Se non ci fosse possibilita’ di partecipare fisicamente ad un incontro resterebbero mailing lists e forum, in cui pero’ raramente e’ facile farsi illustrare con il necessario dettaglio il problema da risolvere ne’ tantomeno esprimere in maniera comprensibile la soluzione, e dunque risultano piu’ una perdita di tempo da ambo le parti che non una risposta effettiva ad un bisogno reale. Alla resa dei conti l’assenza o comunque l’estrema carenza di punti di riferimento per la risoluzione delle pratiche quotidiane si converte in una imbarazzante quantita’ di utenti che abbandonano Linux poco dopo averlo installato e contemplato, frustrati dall’incapacita’ di sistemare il primo banale grattacapo in cui incappano, tornando alla piattaforma operativa di partenza e diventando mine mediatiche vaganti pronte ad esprimere e condividere con amici e conoscenti la propria delusione con un infinito impatto negativo a cascata: una piaga cui pur non avendo dati statistici alla mano credo di non sbagliare attribuendo un ruolo importante nella mancanza di successo plebiscitario da parte del nostro sistema operativo preferito.

In tempi di carenza di developers impiegati a sistemare le cose affinche’ funzionino sempre al primo colpo urge ricorrere ad un mezzo per l’assistenza on-demand, con cui il volenteroso linuxaro possa alla bisogna agire. Urge ingegnerizzare il supporto tecnico.

Nella community Ubuntu gia’ hanno intuito le potenzialita’ di un ipotetico strumento con cui arginare la situazione, massimizzare la resa dei crocerossini digitali ed al tempo stesso evitare tante rogne a chi generosamente si presta, e credo non sia un caso che da qualche release il desktop environment Gnome includa di default un client/server VNC. E sebbene VNC, ovvero il protocollo di condivisione desktop, sia effettivamente il bandolo della matassa ed il punto da cui partire per analizzare la questione, da solo ha una limitata utilita’: ottimo finche’ chi abbisogna di aiuto e’ in legami con chi lo fornisce, meno adatto se il disperato utente non ha amicizie gia’ nel giro o comunque per ottenere un risultato distribuito ed efficiente dalla risorsa umana a disposizione.

Ai tempi d’oro, con gli amici della Torino Linux Task Force in breve notammo che non pochi erano i visitatori che al termine di un intervento chiedevano l’indirizzo mail personale o addirittura il numero di telefono al salvatore di turno, si’ da mantenere un contatto cui aggrapparsi laddove si fosse presentata una ennessimo ostacolo nella loro esperienza linuxofila, ma per ovvie e legittime motivazioni ben pochi erano disposti a lasciare un riferimento col rischio di essere invocati giorno e notte. Alche’ avviamo il progetto LIRA (Linux Infrastructure for Remote Assistance, nome suggerito da d1s4st3r), che avrebbe dovuto essere un mix di VNC, instant messaging e bug tracking con cui il newbie potesse lanciare una richiesta di soccorso da gestire poi in una rete di volontari i quali, dato un momento libero e la disposizione d’animo preferita, potessero connettersi e fare quanto richiesto, senza l’esposizione di dati personali e con buona pace di tutti. Il progetto naufrago’ quando tempo ed interesse scemarano, e ci accontetammo di metter su un banalissimo forum verso cui dirottare la questua informatica, ma personalmente continuo a reputare l’iniziativa degna almeno di valutazione.

Nella sua incarnazione piu’ semplice e limitata l’idea sarebbe implementabile con un request tracker ed un client VNC: chi riscontra una difficolta’ insormontabile pubblica un messaggio e lascia in esecuzione il server di condivisione grafica aperto, mentre chi e’ disposto a dare una mano (debitamente identificato ed autorizzato, per impedire a malintenzionati di insinuarsi negli altrui PC col pretesto dell’assistenza) quando vuole e quando ha tempo consulta la lista di richieste in attesa ed a propria discrezione se ne accolla una. Certo e’ non sempre fattibile (a causa di reti coperta da NAT) e non e’ semplicissima da ingaggiare per l’utente (perche’ comunque deve installare un server VNC e provvedere manualmente a qualche configurazione ed informazione), ma sarebbe almeno un inizio. Strumenti piu’ accuratamente scelti (ad esempio Empathy ed il gia’ incluso supporto per il remote desktop su tube XMPP) fornirebbero una ulteriore ottimizzazione, ed insomma quasi tutto potrebbe essere trattato in prima istanza anche senza una piattaforma software ad-hoc (che andrebbe sviluppata con i tempi e le cure dovute).

Laddove una iniziativa del genere dovesse impiantarsi ed essere adeguatamente promossa dai LUG ed altri enti, una ristretta cerchia di volontari riuscirebbe a far fronte ad un buon numero di richieste su tutto il territorio nazionale pur godendo della massima liberta’ di azione potendo scegliere quando e di cosa occuparsi di volta in volta, e dunque contribuire nel tempo libero ad arginare la fuga di utenti facendo quel che si e’ sempre fatto, ovvero dare una mano ad una persona in difficolta’. Sempre meglio configurare una stampante ad un aspirante linuxaro a 300 chilometri di distanza che non passare la serata a guardare l’Isola dei Famosi.

Tra tutti i componenti della community i buoni samaritani, competenti e pazienti, non mancano: fornendo loro gli strumenti adeguati essi rappresentano il servizio di help-desk piu’ potente al mondo.

Everything you wanted to know and didn’t know to ask.  Click here.

OK, from my experience the system VNC service (once you actually get it working) is shit and a resource hog eg when activated it will be playing nice but as soon as you connect to your appletv it will consume all your clock cycles (no cpu time for anything else) AND when you disconnect it continues to be a whore. You can kill the process which fixes the problem then the deamon respawns a VNC process back to its former nice self.

ENTER VINE SERVER

a numb nut is giving everyone the impression that Vine Server 2.2 is the only one that works on AppleTV, this isnt the case. The most recent version 3.0 functions perfectly fine, unlike version 2.2, version 3.0 will not let a client connect until they choose to set/not set a password. Once this option is selected it works fine……will all those benefits in 3.0….whatever the hell they are

I finally broke down and got an iPhone.

To be fair this has been in the works for a while.  I’ve been following the development of the iPhone since the first one came out, and have a theory that it will play a fairly pivotal role in the future of personal computing and computing in general, but that’s a topic for another post.  Some time ago I made a deal with myself that if I could come up with five applications on the iPhone that would significantly change how I do KAP in the field, I would be in the market for one.  That happened a while ago, but I still held out.  When looking at something like this, it’s hard to know if the decision is being made for legitimate reasons, or simply because it’s a cool gadget.  I erred on the side of cool gadget, and waited.  It was finally a combination of three things that convinced me to get one:

1. I was due for an upgrade on my existing cell pone
2. The ATT website had refurbished 16GB 3G iPhones listed for $99
3. One of my co-workers let me play with her iPhone long enough to completely fall in love with it

Ok, so in the end it’s still probably the cool gadget factor that pushed me over the top, but I did have five applications that I will use when I’m out KAPing:

1. GPS – Prior to this, I was in the market for a small handheld GPS.  I was looking long and hard at the DeLorme PN-40 for some time, but the price tag kept me from taking that plunge.  That the iPhone comes with a GPS that applications can actually access went a long way toward convincing me that this was a viable route.  The performance of the DeLorme likely exceeds what the iPhone will do, but if I was after the ultimate in accuracy I would be looking at the higher end Trimble hardware, all of which is seriously out of my price range.  And from the testing I’ve done the iPhone GPS is plenty accurate for my needs.
2. Google Earth – When the iPhone first came out, a fellow KAPer named Cris Benton picked one up.  Shortly after, he described a particularly difficult session where he needed to fly over a rail yard in order to get his camera in position over a particular subject.  The rail yard was in use, so there was no way to walk through it.  Instead he pulled up his location on Google Earth, visually determined the direction of the wind, and given his kite’s line angle he calculated how much line he needed to let out to get his camera in the correct position.  It worked like a charm.  With the addition of the integrated GPS in the iPhone 3G, this becomes even easier.
3. Anemometer – Yes, there is an anemometer for the iPhone.  It’s a $0.99 application, and is limited to a 0-25mph wind range, but at the cost it’s well worth it as a backup for my Kestrel 2000 anemometer.  I have yet to test this in the field, but from what other people have said it’s typically good to +/- 1 knot, and switching units is trivial.  Before trusting it I plan to run it in side-by-side trials against my Kestrel.
4. Inclinometer – The iPhone 3G has a 3-axis accelerometer built into it.  This has set the stage for a number of apps that replicate the behavior of a carpenter’s bubble level.  But for kiting I was after an inclinometer that would tell me the angle of my kite line.  Turns out there are a whole host of these as well.  The one I got was free off the iPhone App site.
5. Safari Web Browser – The pre-paid data plan on the iPhone makes using the integrated web browser a real no-brainer.  You can’t rack up data charges by using it, so there’s no reason not to.  Also, since the Safari browser on the iPhone is a full-blown browser, you can hit practically any web site and view it the same way you would on a full-blown computer.  This lets me bring up the local wind forecast while I’m in the field, and to check current conditions at a number of weather stations to see if conditions are changing.  I can also use this to cruise Flickr when I fly at a new location to see if there are any interesting subjects nearby.

In addition, there are a number of non-KAP applications I’m using for other reasons.  The notepad and alarm clock are particularly nice.  The iPhone will also take voice memos, which is great for taking notes while KAPing since writing while managing a radio and kite winder is asking for trouble.  I also installed issh, which is an inexpensive combination ssh, telnet, and VNC client.  I’m no longer in the UNIX sysadmin line of work, but I still do run machines at home and at work.  Now I can get to them from practically anywhere.  I also find I’m using the iPod functionality more than I thought I would, since all my music will fit on my iPhone.  The photo gallery application also makes it easy to pack a large number of KAP images on my iPhone so I can show them to people when they ask what I’m doing. Oh, and it’s also a pretty good phone.

All in all I’m more than pleased with it.  I’ve already taken the small portfolio out of my KAP bag, which saves a fair bit of weight and space.  If the anemometer works out well, I may start keeping my Kestrel at home on longer KAP hikes.  The inclinometer, GPS, Google Earth, and readily available wind forecasts are all new, and I haven’t really had a chance to see how much I will use them, or what effect they will have on my work flow in the field.  But already it’s an improvement.  Can’t beat that.

- Tom

As mentioned before, I like to run the Windows proxy software Ultrasurf on Linux.

Some time ago, I made a simple script, that keeps the connection alive by sending data through it from time to time. Two weeks ago I decided to advance it and give it a new name, “ultrasurf-tools”. This piece of bash code was able to completely hide the GUI and run it like a Unix daemon then.

A few days ago however, I decided to push the development even further and turn it into a full Unix daemon. That means automatic installation of the two needed DLL files, automatic download and update of Ultrasurf and even automatic setup of an own user with his own wineprefix and TightVNC settings. So basically one just needs to install that daemon and as soon as it gets started, everything works out of the box.

It basically does its job by now, except that there is still a little bug. When your internet disconnects, Ultasurf tries to connect again for an infinite amount of time, but it somehow does not trigger wget’s timeout (which I use to check whether we are online or not). Thus not only Ultrasurf hangs, but the daemon does not realize it and so nothing happens at all. As soon as I fix this, I will put an official release of the script on its brand new homepage.

Also you may have figured out from the title of this article, that I gave the software a new name. Why? Because ultrasurf-tools might be fine for a little bash script, but as a full functionally daemon, I’d rather use a name that is not related to another software’s name. So I came up with ghostship (metaphor for the invisibility of your IP as well as the invisibility of the GUI).

More information on the official homepage.

Recruiters target Nashville’s life-sciences sector on Venture Nashville.

This link will take you to another blog that did a pretty good job describing some of the work I do.

Milt Capps, the author of this blog, is an experienced journalist who has watched the VC and technologoy world evolve over a number of years and he has a pretty good perspective.

I hope you enjoy the article and I encourage you to add Milt to your reading list.

Широкое распространение торговых сетей выходящих далеко за рамки одного города, сегодня ставят новые задачи перед отделом IT автоматизации.

Сегодня трудно себе представить торговую организация или компанию, в которой не было бы ни одного компьютера, а следовательно и персонала занимающегося техническим обслуживанием компьютеров. Компьютеры бухгалтеров, менеджеров, кассиров расположены далеко друг от друга и связаны между собой в сеть. Все торговые операции, так или иначе, проходят через компьютер и заносятся в базу данных компании, и, конечно же, когда происходит сбой в работе какого-либо компьютера, то вся цепочка автоматизированного процесса прерывается и работа останавливается. Чтобы возобновить рабочий процесс, необходимо как можно быстрее устранить неисправность или оказать техническую поддержку пользователю. Самым быстрым и эффективным способом решения поставленных задач является удаленное подключение к компьютеру для решения возникших проблем.

Remote Office Manager – это не только мощное средство удаленного администрирования, но и современный инструмент повышения эффективности бизнеса торгового предприятия. Прикладное решение позволяет в комплексе автоматизировать задачи оказания технической помощи удаленным пользователям, настройке компьютеров и управления ими. Программа полностью совместима с последней разработкой компании Microsoft – ОС Windows 7, обладает серьезной системой безопасности, широкими возможностями настройки как для работы в локальных сетях, так и в Интернете.

Программа представляет клиент-серверную систему. Серверная часть устанавливается на удаленных компьютерах и позволяет подключаться к ним с помощью клиентской части, которая устанавливается на компьютере администратора.

Программа автоматизирует решение следующих технических задач:
• Удаленное управление и администрирование компьютеров.
• Оказание технической поддержки удаленным пользователям.
• Проведение инвентаризации компьютерного оборудования и ПО.
• Контроль использования рабочего времени сотрудниками.
• Возможность подключения удаленных сотрудников.

Удаленное управление и администрирование компьютеров
Администрирование сети торговой компании не простая задача, парк компьютеров может быть распределен не по одному городу, отделы продаж, склад, центральный офис и т.д., ко всем компьютерам должен быть удаленный доступ для IT сотрудников. Чтобы было легче ориентироваться и управлять всеми компьютерами, в Remote Office Manager есть возможность рассортировать их по отдельным группам, а также можно нарисовать полноценную карту сети с расположенными компьютерами и другим офисным оборудованием. Для быстрого развертывания программы в сети, в Remote Office Manager есть встроенный поиск и средства удаленной установки программы, что позволяет быстро установить и настроить программу на большом количестве компьютеров.

В главном окне программы отображаются эскизы экранов удаленных компьютеров и их статусы, что позволяет постоянно контролировать их состояние. По мере надобности можно быстро подключиться к нужному компьютеру в одном из доступных режимов.

Режимы удаленного управления:
• Просмотр и управление рабочим столом удаленного компьютера. Позволяет подключаться к удаленному рабочему столу и управлять им при помощи мышки и клавиатуры. При необходимости можно заблокировать удаленный компьютер и вывести на его экран уведомляющее сообщение о том, что за компьютером работает удаленный администратор. Реализована возможность удобного перетаскивания файлов на удаленный рабочий стол и обратно. Множество опций позволяет настроить цветопередачу, качество картинки и нагрузку на сеть во время работы.
• Передача файлов. Позволяет обмениваться файлами с удаленным компьютером. Закладки позволяют быстро перемещаться к нужным каталогам и файлам. Поддерживается докачка файлов и функции Drag&Drop.
• Диспетчер задач управляет процессами и сервисами и окнами удаленной системы, с помощью него можно останавливать или запускать процессы и сервисы, контролировать их рабочее состояние.
• Управление питанием. Дает возможность выключать, перезагружать, завершать сеанс на удаленном компьютере. Используя дополнительную функцию Wake-On-LAN можно включить удаленный компьютер.
• Терминал. Данный режим предоставляет терминальный доступ к удаленной системе, проще говоря, доступ к командной строке удаленного компьютера. Это позволяет управлять компьютером, используя минимум сетевых и процессорных ресурсов.
• Текстовый чат. С помощью чата можно вести переписку с удаленным пользователем или группой пользователей.
• Диспетчер устройств собирает информацию об удаленном программном обеспечении и установленном оборудование.
• Подключение с помощью RPD, стандартного протокола удаленного рабочего стола Windows.
• Запись экрана, записывает происходящее на удаленном рабочем столе в специальный видео файл.

Оказание технической поддержки удаленным пользователям
Часто у удаленных пользователей возникают проблемы при работе с компьютером. Иногда из-за простого непонимания или незнания какого-либо программного обеспечения. Чтобы помочь удаленному пользователю достаточно небольшой консультации по чату или подключения к рабочему столу. При работе с удаленным рабочим столом можно скрыть свои действия от пользователя, заблокировав рабочий стол и управление компьютером. Когда канал связи слабый и возникают задержки при работе с удаленным рабочим столом, в опциях соединения можно отключить заставку на удаленном компьютере, установить экономичный режим передачи данных, изменить палитру, что позволит ускорить работу. Сложности, возникают, когда необходимо подключиться к компьютеру, у которого нет внешнего IP адреса, т.е. компьютер находится за NAT. В Remote Office Manager реализована функция «обратного соединения», в этом случае удаленный компьютер сам инициирует связь с компьютером администратора.

Если удаленный компьютер находиться в другой подсети, и прямого доступа нет, то можно использовать ROM-Server в качестве шлюза для доступа к компьютерам находящимся за ним, опция называется «подключиться через».

Проведение инвентаризации компьютерного оборудования и ПО
При большом количестве компьютеров в организации, и неизбежной смене обслуживающего персонала IT службы, сложно уследить за актуальным состоянием всех компьютеров. Устаревшее оборудование может стать причиной сбоя или выхода из строя компьютера, а программное обеспечение должно быть лицензионным, так как проверки в наше время не редкость, а штраф может быть не маленьким. Рано или поздно возникнет необходимость проведение инвентаризации всего парка компьютеров. Remote Office Manager позволяет быстро провести инвентаризацию и собрать все данные о компьютерах в виде отчетов. В отчетах содержатся данные об установленном программном и аппаратном обеспечении с кратким описанием основных параметров.

Контроль использования рабочего времени сотрудниками
На своем рабочем месте пользователи могут заниматься чем угодно, но только не работой, смотреть фильмы, играть, посещать свои любимые сайты в Интернете и т.д., в результате на компьютере может появиться множество лишней информации и вирусов, придти большой счет за трафик Интернет или снизиться производительность труда. Чтобы не допустить этого, администратору необходимо все время контролировать удаленных пользователей даже в свое отсутствие на рабочем месте. Remote Office Manager позволяет настроить удаленную запись экрана, которая будет записывать все действия пользователя на его рабочем месте, что позволит оптимизировать работу всего персонала и, как следствие, улучшить производительность всей организации.

Возможность подключения удаленных сотрудников
С помощью Remote Office Manager можно организовать удаленный доступ для работы сотрудников находящихся в отъезде или отпуске. Программа может работать в т.н. переносимом (portable) виде, с возможностью работы с переносимого носителя, например с флеш-карты. Таким образом, можно подключиться к своему рабочему месту с любого компьютера, подключенного к Интернету.

При подключении и работе все данные передаются по зашифрованному каналу. В программе существует возможность настройки встроенного IP фильтра, позволяющего разрешить или запретить доступ к компьютеру с определенных IP адресов.

Заключение
Remote Office Manager является серьезным средством автоматизации удаленного управления и администрирования торговой организации, программа может использоваться как отдельное средство автоматизации, так и в совокупности с другим программным обеспечением. Remote Office Manager можно скачать с официального сайта компании производителя “Aledensoft“.

For the past few weeks, AppleVNCServer (aka screen sharing) crashes when you connect to it.  It’s on a Mac mini running Mac OS X Server 10.5.8.  Here’s the relevant bit from system.log:

Oct  3 14:17:35 minnie ReportCrash[12942]: Formulating crash report for process AppleVNCServer[12874]
Oct  3 14:17:36 minnie com.apple.launchd[264] (com.apple.ScreenSharing.server[12874]): Exited abnormally: Segmentation fault
Oct  3 14:17:37 minnie ReportCrash[12942]: Saved crashreport to /Users/will/Library/Logs/CrashReporter/AppleVNCServer_2009-10-03-141730_minnie.crash using uid: 501 gid: 20, euid: 501 egid: 20

Nothing too interesting there, so here’s the crash log it mentions:

Process:         AppleVNCServer [12874]
Path:            /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/MacOS/AppleVNCServer
Identifier:      AppleVNCServer
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [264]

Date/Time:       2009-10-03 14:17:30.662 -0400
OS Version:      Mac OS X Server 10.5.8 (9L34)
Report Version:  6
Anonymous UUID:  1DFDDD4A-5259-4417-A19F-8DA81EA911FC

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread:  4

Thread 0:
0   libSystem.B.dylib             	0x90d51286 mach_msg_trap + 10
1   libSystem.B.dylib             	0x90d58a7c mach_msg + 72
2   com.apple.CoreFoundation      	0x9098de7e CFRunLoopRunSpecific + 1790
3   com.apple.CoreFoundation      	0x9098eb04 CFRunLoopRun + 84
4   com.apple.AppleVNCServer      	0x00005a4f 0x1000 + 19023
5   com.apple.AppleVNCServer      	0x00002675 0x1000 + 5749
6   com.apple.AppleVNCServer      	0x00025636 0x1000 + 149046
7   com.apple.AppleVNCServer      	0x00001fd9 0x1000 + 4057

Thread 1:
0   libSystem.B.dylib             	0x90d819c6 kevent + 10
1   ...ple.CoreServices.CarbonCore	0x95789057 PrivateMPEntryPoint + 56
2   libSystem.B.dylib             	0x90d82155 _pthread_start + 321
3   libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 2:
0   libSystem.B.dylib             	0x90d883ca select$DARWIN_EXTSN$NOCANCEL + 10
1   com.apple.AppleVNCServer      	0x00004c9b 0x1000 + 15515
2   ...ple.CoreServices.CarbonCore	0x95789057 PrivateMPEntryPoint + 56
3   libSystem.B.dylib             	0x90d82155 _pthread_start + 321
4   libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 3:
0   libSystem.B.dylib             	0x90d512da semaphore_timedwait_trap + 10
1   ...ple.CoreServices.CarbonCore	0x9579c47b MPWaitOnSemaphore + 125
2   com.apple.AppleVNCServer      	0x00006be5 0x1000 + 23525
3   ...ple.CoreServices.CarbonCore	0x95789057 PrivateMPEntryPoint + 56
4   libSystem.B.dylib             	0x90d82155 _pthread_start + 321
5   libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 4 Crashed:
0   com.apple.AppleVNCServer      	0x00037a1e 0x1000 + 223774
1   com.apple.AppleVNCServer      	0x000157c8 0x1000 + 83912
2   com.apple.AppleVNCServer      	0x00014a5f 0x1000 + 80479
3   com.apple.AppleVNCServer      	0x00008fa4 0x1000 + 32676
4   ...ple.CoreServices.CarbonCore	0x95789057 PrivateMPEntryPoint + 56
5   libSystem.B.dylib             	0x90d82155 _pthread_start + 321
6   libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 5:
0   libSystem.B.dylib             	0x90d51286 mach_msg_trap + 10
1   libSystem.B.dylib             	0x90d58a7c mach_msg + 72
2   com.apple.framework.IOKit     	0x911a94b7 io_connect_method + 592
3   com.apple.framework.IOKit     	0x911333c6 IOConnectCallMethod + 300
4   ...er.AppleIntelGMA950GLDriver	0x00782c95 glrReadPixels + 1973
5   GLEngine                      	0x005ff144 glReadPixels_Exec + 2004
6   libGL.dylib                   	0x93eecaa9 glReadPixels + 73
7   com.apple.AppleVNCServer      	0x000155ee 0x1000 + 83438
8   com.apple.AppleVNCServer      	0x00009d87 0x1000 + 36231
9   ...ple.CoreServices.CarbonCore	0x95789057 PrivateMPEntryPoint + 56
10  libSystem.B.dylib             	0x90d82155 _pthread_start + 321
11  libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 6:
0   libSystem.B.dylib             	0x90d5846e __semwait_signal + 10
1   libSystem.B.dylib             	0x90d82dcd pthread_cond_wait$UNIX2003 + 73
2   libGLProgrammability.dylib    	0x93f43b32 glvmDoWork + 162
3   libSystem.B.dylib             	0x90d82155 _pthread_start + 321
4   libSystem.B.dylib             	0x90d82012 thread_start + 34

Thread 4 crashed with X86 Thread State (32-bit):
  eax: 0x00807c00  ebx: 0x00000000  ecx: 0x000b5000  edx: 0xffffeaa8
  edi: 0x000b5000  esi: 0x125d40a8  ebp: 0xb0226c28  esp: 0xb0226854
   ss: 0x0000001f  efl: 0x00010202  eip: 0x00037a1e   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037
  cr2: 0x00037a10

Binary Images:
    0x1000 -    0x4dff7  com.apple.AppleVNCServer 3.3.1 (3.3.1) <5b4a7fdb0c13de88d2d0bd7c309047ed> /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/MacOS/AppleVNCServer
   0xcb000 -    0xe7ff7  GLRendererFloat ??? (???) <7badea5e2b8167c0e6391623bb46140a> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
  0x5b2000 -   0x737fe3  GLEngine ??? (???) <052e02d9a452a45d014ffbd2a84a4e7c> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
  0x765000 -   0x7beff7  com.apple.driver.AppleIntelGMA950GLDriver 1.5.48 (5.4.8) <806d3030842b46995c46c9059046f2fc> /System/Library/Extensions/AppleIntelGMA950GLDriver.bundle/Contents/MacOS/AppleIntelGMA950GLDriver
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???) <458eed38a009e5658a79579e7bc26603> /usr/lib/dyld
0x9020b000 - 0x90264ff7  libGLU.dylib ??? (???) <64d010e31d7596bd8f9edc6e027d1d0c> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x9034d000 - 0x90354ffe  libbsm.dylib ??? (???)  /usr/lib/libbsm.dylib
0x9036d000 - 0x9077dfef  libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x9077e000 - 0x907dbffb  libstdc++.6.dylib ??? (???) <04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x907dc000 - 0x907dcffd  com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x907dd000 - 0x907ebffd  libz.1.dylib ??? (???) <5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x90890000 - 0x9091afe3  com.apple.DesktopServices 1.4.8 (1.4.8)  /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x9091b000 - 0x90a4efe7  com.apple.CoreFoundation 6.5.7 (476.19)  /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90a94000 - 0x90a94ff8  com.apple.ApplicationServices 34 (34) <8f910fa65f01d401ad8d04cc933cf887> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x90cfe000 - 0x90d4fff7  com.apple.HIServices 1.7.1 (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x90d50000 - 0x90eb7ff3  libSystem.B.dylib ??? (???)  /usr/lib/libSystem.B.dylib
0x90eb8000 - 0x90f4bfff  com.apple.ink.framework 101.3 (86)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x90f52000 - 0x90f8cfe7  com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x90f8d000 - 0x90f96fff  com.apple.speech.recognition.framework 3.7.24 (3.7.24)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x91073000 - 0x91074ffc  libffi.dylib ??? (???)  /usr/lib/libffi.dylib
0x910f3000 - 0x910f8fff  com.apple.CommonPanels 1.2.4 (85)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x9112e000 - 0x911bbff7  com.apple.framework.IOKit 1.5.2 (???) <7a3cc24f78f93931731203854ae0d891> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x911bc000 - 0x91243ff7  libsqlite3.0.dylib ??? (???)  /usr/lib/libsqlite3.0.dylib
0x91244000 - 0x912d1ff7  com.apple.LaunchServices 292 (292)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x912d2000 - 0x912f0ff3  com.apple.DirectoryService.Framework 3.5.6 (3.5.6) <48d78074835db0d5fe5b632991c21b1b> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x912f1000 - 0x91310ffa  libJPEG.dylib ??? (???) <50b881dd5a5795d38405c9c88c2806fa> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91311000 - 0x91350fef  libTIFF.dylib ??? (???) <801873cbd85ba7bdfe7646fe97a54ca3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x92330000 - 0x92501ffb  com.apple.security 5.0.5 (36371) <1f7f48b36bc90d114220cc81e4e4694f> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92666000 - 0x92693feb  libvDSP.dylib ??? (???)  /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x92694000 - 0x9273bfec  com.apple.CFNetwork 438.14 (438.14) <5f9ee0430b5f6319f18d9b23e777e0d2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x9278e000 - 0x9278effd  com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x9278f000 - 0x927a4ffb  com.apple.ImageCapture 5.0.2 (5.0.2) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x92978000 - 0x92978ffb  com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x92cc7000 - 0x92cc7ffa  com.apple.CoreServices 32 (32) <2fcc8f3bd5bbfc000b476cad8e6a3dd2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x92cc8000 - 0x92fd0fe7  com.apple.HIToolbox 1.5.6 (???)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x92fd1000 - 0x92fedff3  libPng.dylib ??? (???) <271373dd41f56369a3dfca0ed2be579a> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x92fee000 - 0x93017fff  libcups.2.dylib ??? (???) <3f0976287f63781607864f6586ad7229> /usr/lib/libcups.2.dylib
0x93018000 - 0x9303cfff  libxslt.1.dylib ??? (???)  /usr/lib/libxslt.1.dylib
0x9303d000 - 0x9303dffc  com.apple.audio.units.AudioUnit 1.5 (1.5) /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x93075000 - 0x930f4ff5  com.apple.SearchKit 1.2.2 (1.2.2) <3b5f3ab6a363a4d8a2bbbf74213ab0e5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x931ef000 - 0x93296feb  com.apple.QD 3.11.56 (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x932c1000 - 0x93413ff3  com.apple.audio.toolbox.AudioToolbox 1.5.2 (1.5.2) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x93414000 - 0x9342afff  com.apple.DictionaryServices 1.0.0 (1.0.0)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x93453000 - 0x9346bff7  com.apple.CoreVideo 1.6.0 (20.0)
 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x934a7000 - 0x93587fff  libobjc.A.dylib ??? (???) <3ca288b625a47bbcfe378158e4dc328f> /usr/lib/libobjc.A.dylib
0x93590000 - 0x93594fff  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x93596000 - 0x93613fef  libvMisc.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x93614000 - 0x93652fff  libGLImage.dylib ??? (???) <2e570958595e0c9c3a289158223b39ee> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x93653000 - 0x93a11fea  libLAPACK.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x93a12000 - 0x93a18fff  com.apple.print.framework.Print 218.0.3 (220.2) <8c541d587e4068a5fe5a5ce8ee208516> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x93a19000 - 0x93a1bfff  com.apple.securityhi 3.0 (30817) <2b2854123fed609d1820d2779e2e0963> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x93a1c000 - 0x93a2cffc  com.apple.LangAnalysis 1.6.5 (1.6.5)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x93a2d000 - 0x93ca9fe7  com.apple.Foundation 6.5.9 (677.26)  /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x93caa000 - 0x93d24ff8  com.apple.print.framework.PrintCore 5.5.4 (245.6) <9ae833544b8249984c07544dbe6a97fa> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x93d25000 - 0x93ddffe3  com.apple.CoreServices.OSServices 228 (228)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x93ee7000 - 0x93ee7fff  com.apple.Carbon 136 (136) <98a5e3bc0c4fa44bbb09713bb88707fe> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x93ee8000 - 0x93eeaff5  libRadiance.dylib ??? (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x93eeb000 - 0x93ef7ffe  libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x93ef8000 - 0x93f10fff  com.apple.openscripting 1.2.8 (???)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x93f11000 - 0x93f1bfeb  com.apple.audio.SoundManager 3.9.2 (3.9.2) <0f2ba6e891d3761212cf5a5e6134d683> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x93f1c000 - 0x943edfbe  libGLProgrammability.dylib ??? (???)  /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x943ee000 - 0x94430fef  com.apple.NavigationServices 3.5.2 (163) <7f4f1766414a511bf5bc68920ac85a88> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x94456000 - 0x94485fe3  com.apple.AE 402.3 (402.3)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x94486000 - 0x94503feb  com.apple.audio.CoreAudio 3.1.2 (3.1.2) <782a08c44be4698597f4bbd79cac21c6> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x94504000 - 0x9450bfe9  libgcc_s.1.dylib ??? (???)  /usr/lib/libgcc_s.1.dylib
0x9450c000 - 0x9452afff  libresolv.9.dylib ??? (???) <0e26b308654f33fc94a0c010a50751f9> /usr/lib/libresolv.9.dylib
0x94592000 - 0x945a2fff  com.apple.speech.synthesis.framework 3.7.1 (3.7.1) <9a71429c74ed6ca43eb35e1f78471b2e> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x945a3000 - 0x94636ff3  com.apple.ApplicationServices.ATS 3.7 (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x94637000 - 0x9463ffff  com.apple.DiskArbitration 2.2.1 (2.2.1)  /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9465b000 - 0x946a4fef  com.apple.Metadata 10.5.8 (398.26)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x946a5000 - 0x946a5ff8  com.apple.Cocoa 6.5 (???)  /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x946a6000 - 0x946aafff  libGIF.dylib ??? (???) <3c7100e80b7f7ca8809cf9512c1a6004> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x946ab000 - 0x9475dffb  libcrypto.0.9.7.dylib ??? (???) <8ac6abef4b3bb125c8bf84634421bcee> /usr/lib/libcrypto.0.9.7.dylib
0x94897000 - 0x94978ff7  libxml2.2.dylib ??? (???) <4d54971007e14f8d80e6889ee1111f21> /usr/lib/libxml2.2.dylib
0x95206000 - 0x95206ffd  com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x95207000 - 0x95340ff7  libicucore.A.dylib ??? (???)
 /usr/lib/libicucore.A.dylib
0x95341000 - 0x956defef  com.apple.QuartzCore 1.5.8 (1.5.8) <18113e06d296230d63a63b58baf35f55> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x95708000 - 0x9573ffff  com.apple.SystemConfiguration 1.9.2 (1.9.2) <41d5aeffefc6d19d471f51ae0b15024f> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x95740000 - 0x95a1aff3  com.apple.CoreServices.CarbonCore 786.11 (786.14)  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x95a1b000 - 0x95a1efff  com.apple.help 1.1 (36)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x95aa7000 - 0x95b6eff2  com.apple.vImage 3.0 (3.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x95b6f000 - 0x9636dfef  com.apple.AppKit 6.5.9 (949.54) <4df5d2e2271175452103f789b4f4d8a8> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x967de000 - 0x968c6ff3  com.apple.CoreData 100.2 (186.2) <44df326fea0236718f5ed64084e82270> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x96936000 - 0x96961fe7  libauto.dylib ??? (???) <4f3e58cb81da07a1662c1f647ce30225> /usr/lib/libauto.dylib
0x9699b000 - 0x96a4bfff  edu.mit.Kerberos 6.0.13 (6.0.13)  /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x96a4c000 - 0x96aa8ff7  com.apple.htmlrendering 68 (1.1.3)  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x96cae000 - 0x96cbbfe7  com.apple.opengl 1.5.10 (1.5.10)  /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x96cbf000 - 0x96e07ff7  com.apple.ImageIO.framework 2.0.6 (2.0.6) <7f73ef328c8e8566f3f204b5a540a7f0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x96e08000 - 0x96e62ff7  com.apple.CoreText 2.0.4 (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x96e79000 - 0x96f44fef  com.apple.ColorSync 4.5.3 (4.5.3) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x96f45000 - 0x975e5fef  com.apple.CoreGraphics 1.409.4 (???)  /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

Here’s where I reach the limits of my knowledge.  It looks like the system is pointing its finger at thread 4 as the culprit, and thread 4 looks like it’s loaded up the libSystem and Carbon libraries.  So perhaps one of those core system libraries are corrupted?  I tried re-applying the 10.5.8 combo update (since that will overwrite a lot of libraries with the latest version, just in case) to no effect, and I removed all the VNC- and Remote Desktop-related files in /Library/Preferences/ without any luck, either.

Obviously I could do an archive or erase and install and it’d take care of the issue, but I’m interested in actually sussing out the cause and pinpointing it.  Any suggestions are welcome at this point!

UPDATED – Nov. 19th, 2009
A few days after posting this I noticed that while connecting to the VNC server with Mac OS X’s built-in VNC client (called by choosing “Connect to Server…” from the “Go” menu in Finder and providing it a “vnc://ip.goes.here” URL) incurs the crash of the server, connecting to it with Apple’s Remote Desktop application doesn’t.  So, I’ve got a workaround, but still no solution.  I’m going to try to chase this down in the next couple weeks, hopefully I’ll be able to pinpoint the cause.

Update: Please use the newer and improved version of this script: ghostship.

In one of my earlier articles, I released a little script which keeps Ultrasurf connected by generating traffic every minute. Today I’ve gone one step further and made a script that does the following:

• Ultrasurf starts invisible in its very own (vnc)X-server, which makes it possible to start it before you even started your X session
• Generates traffic every 20 seconds and by doing that it checks at the same time whether Ultrasurf is still connected to the internet
• It writes a status-file which you can use with conky to display whether Ultrasurf is currently working or not
• When Ultrasurf is down, the script tries a few more times (with less waiting between the tries) and then it restarts the whole vncserver, thus killing everything inside it and starting clean (by doing normal restarts, sometimes Ultrasurf binds the wrong or simply no port)

Ready? Here’s my step by step tutorial:

• install Ultrasurf (in its own wineprefix)
• install tightvnc
• run vncserver && vncserver -kill :1 once to set a password for your vnc server
• open up ~/.vnc/xstartup and copy paste the following

#!/bin/sh

if [ $VNCDESKTOP = "ultrasurf-tools" ]; then

# you'll need to edit this line, so that it points

# to your Ultrasurf installation

WINEPREFIX=/home/you/.wine-ultrasurf wine c:/u.exe

else

xrdb $HOME/.Xresources

xsetroot -solid grey

xterm -geometry 80x24+10+10 -ls -title \

"$VNCDESKTOP Desktop" &

twm &

fi

• paste the following to a file called ~/ultrasurf-tools or something and give it the executable flag

#!/bin/bash

# configuration

# warning, statusfile will get removed!

statusfile=~/.ultrasurf

# internal variables

errors=0

# functions

function restart_ultrasurf {

vncserver -kill :96

vncserver :96 -name "ultrasurf-tools" -localhost

errors=0

# echo "sleeping for 20 seconds"

sleep 20

}

# the main loop

# echo "starting ultrasurf..."

rm "$statusfile"

restart_ultrasurf

while [ 1 ];do

# echo "performing connection check..."

dyndns=`http_proxy="127.0.0.1:9666"\

wget --no-cookies checkip.dyndns.org -O - -q -nv`

if [ -z "$dyndns" ]; then

let errors+=1

# echo "error ($errors): couldn't request\

data through ultrasurf."

if [ $errors = 2 ]; then

rm "$statusfile"

fi

if [ $errors = 4 ]; then

# echo "error limit reached! restarting ultrasurf..."

restart_ultrasurf

else

# echo "sleeping for 3 seconds"

sleep 3

fi

else

errors=0

# echo "success. sleeping for 20 seconds..."

touch "$statusfile"

sleep 20

fi

done

• to use the statusfile with conky, add a line similar to this one to the TEXT area (make sure you use your username):

ultrasurf: ${if_existing /home/you/.ultrasurf}${color}online$else${color red}offline$endif

• you can now add this to your /etc/rc.local in order to start ultrasurf before you start your X (the result will be that as soon as your X is started, you are ready to go and do not need to wait for Ultrasurf anymore):

su yourusername -c ~/ultrasurf-tools &

• if you would like to check what is going on, execute vncviewer :96 (but you usually don’t need that)

Our local church has a wonderful problem: we have too many people for our facilities.  We are in the process of expanding, but in the mean time, we are using our choir room as an overflow room during worship services.  So, we pipe in an audio/video feed from the sanctuary to this overflow room as well as to several TVs in the nursery area.   The choir room and nursery suite are in a new part of our facilities, and as part of the building plan we required that gigabit ethernet be ran to all new rooms.  This has made the implementation of a video distribution system much easier, although a similar system should be possible using 100Mb or even Wireless-N ethernet.

This system begins with an analog A/V to firewire converter box.  This converts an S-video video signal plus the audio signal into a digital DV format that can be accessed live over firewire to a computer.  This converter is connected to a PC running Linux.  We use a combination of dvgrab and VLC to receive the stream from the converter, transcode it, and broadcast it over the network.  In the overflow room we have a PC that is currently running Windows Vista and uses VLC to receive the stream and display it on a projector connected to it.  The overflow room machine’s video card has S-video out that we run through an analog video amplifier/converter and broadcast it over our closed-circuit coax network primarily to the nursery area.

What has been really nice about this set up is that it is all controlled from the single Linux machine.  From there we can remotely power on the machine in the overflow room simply by clicking an icon on the desktop.  When that machine starts we connect to it via VNC (UltraVNC) to log in as the proper user.  That user’s account automatically starts VLC and tries to connect to the video stream.  VLC can be set to retry indefinitely in case of error, so if the stream stops or has not started yet, then it will keep trying until things are working again.  Finally, we have a single icon on the desktop of the Linux machine that when clicked will start/stop the stream.  So, from a user’s point of view, all they have to do is power up the converter, click an icon to turn on the remote Windows computer, log in remotely (again we have an icon for that), and click the “start stream” icon.

We plan on do more with this system in the future.  We are currently only streaming and not recording the digital stream (we have a DVD recorder that is used to record directly from the camera).  We would like to start recording the digital stream and then we can automatically do things like strip off the audio to make audio CDs, upload it to a website or youtube, or even turn it into a podcast.  All these things would happen automatically when the service was concluded.

Since the video is being sent over our network, it makes things very flexible for us.  We recently had a very large event, and we were able to set up another ad-hoc viewing area by hooking up a laptop with a wireless network connection to a mobile TV.  Also, our church has multiple services, and early in this implementation there were some issues during the service that I do not normally attend, but since we had remote access set up, I was able to troubleshoot and fix the problem remotely.

We had several goals when we implemented this system.

1. Ease of use
   • This is another fairly technical system that was going to be run by a group of volunteers of all technical skill levels.  It had to be easy enough to use so it could be used without much understanding of the underlying details.  This is why the majority of the system is controlled by a few clicks of some icons on the desktop.  No configuration, no fuss.
2. Low cost
   • All the software used to actually handle the recording/streaming/displaying is completely free and open-source.  While our system did require the use of two computers, only the one do the broadcasting needs to be well spec’d.  Also, we actually have a 3 camera remotely controlled camera system, but there is no reason why a church could not start out with a consumer level mini-DV camcorder.  I say mini-DV because all mini-DV camcorders have a firewire output on them.  This was actually what we were planning on using ourselves until the funds became available for the fancier setup.  Converter boxes start around $200 dollars.
3. Redundancy
   • Other than the converter box,  all the components in our system are commonplace  and interchangeable  We are simply using regular PCs running cross-platform free software.  We could mix and match systems as needed if the need did indeed arise.
4. Flexible
   • This design does not restrain us in how it can be used.  As I mentioned above, we have plans to do much more with it with little to no extra cost.

I will not say we did not have any difficulties during the initial stages of implementation, but we now have very few issues and very good quality.

Isn’t it the dream of every slacker to sit in bed, or at the beach, and make it appear like you are putting a full day at the office? Well, there’s an app for that.

Enter the variety of remote control apps for the iPhone, which let you operate your desktop Mac from your iPhone as if you were sitting in front of it. Some of these apps use the common VNC protocol to allow remote control, and others use their own proprietary methods. All of them will let you control your Mac (or a PC) from your iPhone.

Jaadu ($24.99)

Jaadu is the most polished and powerful of all the iPhone remote control clients. It offers SSH encrypted VNC, which is a key feature if you connect to your Mac via public Wi-Fi networks, although the SSH encryption in Jaadu doesn’t operate with Snow Leopard Macs (Jugari promises a fix soon).

The actual remote control is quite intuitive. By default, control is a combination of moving the mouse pointer and sliding the desktop behind it.  You pinch with two fingers to zoom in and out of the remote screen, and the iPhone’s soft keyboard can be used for typing. Jaadu provides a pop-up box for using modifier keys, as well as keys that don’t exist on the iPhone keyboard. It works well for limited typing, but you would not want to write an essay this way. Jaadu includes nice extras such as clipboard transfer and support for a wide variety of VNC servers, including the built-in Mac OS screensharing.  Unfortunately, you do need to modify and configure your firewall to allow SSH, but Jaadu does have software that will attempt to automatically configure it for you.

LogMeIn Ignition ($29.99)

LogMeIn’s primary feature is that it requires zero configuration of the computer being controlled, and it works securely and automatically across all kinds of networks (other remote control clients usually require manual router configuration). The software works with LogMeIn’s suite of Mac and Windows remote control products, and is a polished and powerful piece of commercial software.

After installation, you are presented with a list of computers to which you have access, and that’s all you need to configure it. The actual remote control isn’t as smooth or intuitive as Jaadu.  Your two basic modes are either the background moves or the mouse moves. Similar to Jaadu, LogMeIn has a pop-up keyboard and modifier keys.   Personally, I use this program as my preferred method of remote control because I can easily control a fleet of Macs and PCs.

iSSH ($4.99)

iSSH, like Jaadu, offers integrated encryption of VNC sessions; however, the remote control functionality seems to be thrown in as an afterthought in what is actually a very powerful system administrators’ tool, offering all kinds of remote access including SSH, X11 and telnet.

Similar to other remote control clients, you move the mouse by sliding your finger across the phone’s screen. A very nice feature iSSH offers is a “transparent” view of the keyboard, so you can type while still seeing as much of the remote screen as possible. Actual performance seemed a bit slower than LogMeIn or Jaadu, and the app appears less stable, occasionally crashing. The crashing aside, it’s overall an excellent value.

MochaVNC ($5.99) and MochaVNC Lite (Free)

The Lite version of Mocha is absolutely worthless; it works OK as a viewer, but you can’t do any normal typing, as the developers do not support the Mac’s modifier keys, such as “command,” unless you buy the full version. Neither version offers integrated encryption, and the performance was slow and unreliable. At a dollar more than the more polished and feature-rich iSSH, MochaVNC is not a good value.

RemoteTap ($4.99)

RemoteTap is a “VNC-like” application, although it doesn’t actually use a standard VNC server. Instead, you download the free RemoteTap preference pane on the computer you want to control. This preference pane is much more powerful than normal VNC servers, offering support for advanced features like command macros, multi-touch gestures, and direct access to Spaces, Front Row, and application launching.

RemoteTap’s remote control works very well, with a unique “magnifying glass” interface that expands the area of the remote Mac screen without the need for a lot of manual zooming in and out. Overall, RemoteTap is very polished and feature rich, but it is missing support for standard VNC or encryption, so it is not a good choice for those with a mix of Mac and PCs or who need to connect over the Internet.

RDM+ Remote Desktop ($9.99)

RDM+ Remote Desktop works in a similar manner to LogMeIn, utilizing a central server to enable remote control of Mac and PC desktops from an iPhone without requiring manual configuration of routers or firewalls. You install a small piece of software on the Mac or PC you want to control, and then purchase and install the app on your iPhone. RDM+ Remote Desktop provides the usual basic remote control features; you can pan, zoom, click and drag on the remote computer as well as type text. However, the controls on the iPhone felt awkward and were not as intuitive to use as many of the other remote control apps.

All of these apps have their plusses and minuses. The best value for the money is probably iSSH. The most polished commercial-grade software is LogMeIn. Jaadu is simply the most powerful pure VNC client, and RemoteTap offers some unique Mac-only functionality for LAN use in a home or office. MochaLite works well as a free viewer if you just need very basic functionality.  Which ever way you go, these apps will let you access the desktop of your Mac from anywhere, so go ahead and stay in bed and convince your boss you are sitting at the office.

Żaden człowiek nie lubi być obgadywany. Zdarza się że ludzie udają Twoich dobrych przyjaciół a tak na prawdę obrabiają Ci dupę.
Jeżeli chcemy “podsłuchać” kto co o nas sądzi bardzo łatwo możemy to wykonać. Można to wykonać na kilka sposobów, najprostszym sposobem jest zainstalowanie serwera VNC i podglądanie co kto pisze w mailach, gg, czy też na skype. VNC nie jest zbyt dobrym sposobem, jeżeli wiemy że ktoś obrabia nam dupsko poprzez np. gg
Rozmowy na gadu-gadu możemy podsłuchiwać za pomocą GG-sniffer (by Grzonu), gdzie każda rozmowa jest zapisywana do pliku tekstowego. Sniffer ten obsługuje GG7 i GG8. Po zainstalowaniu biblioteki WinPcap i odpaleniu sniffera na komputerze osoby którą podejrzewamy o “obrabianie dupy” Sniffer ten jest widoczny co na pewno rzuci się w oczy, możemy jednak za pomocą skryptu odpalić program jako usługę ukrytą. Możemy również za pomocą innego oprogramowania ukryć taką aplikację, jednak nie jest to dobre rozwiązanie z tego powodu iż w menedżerze zadań będzie widniała aplikacja. Po wybraniu odpowiedniej metody ukrycia aplikacji możemy co określony czas zgrywać sobie plik z rozmowami poprzez internet
Osoby, które się zorientują o tym sposobie nie będą już pisać żadnych obraźliwych tekstów na nasz temat. Możemy jednak domyślać się że będzie to obrabianie w 4 oczy. Z tym sobie również możemy łatwo poradzić za pomocą podsłuchów na allegro podsłuch na fale radiowe jest to koszt około 10 zł za sztukę, gdy zakupimy kilka takich urządzeń rozstawimy w najbardziej strategicznych miejscach. Następnie będziemy nagrywać sobie takie rozmowy i później je odsłuchiwać
Pozostają jeszcze telefony komórkowe, rozmowy głosowe oraz SMSy tu też nie jest tak ciężko jak by się wydawało. Urządzenie do podsłuchu rozmów GSM to koszt około 1200 zł (a możemy go używać do woli w różnych sytuacjach). Czytanie SMSów nie jest też niczym trudniejszym wystarczy że za pomocą metod socjotechniki, oraz włączonym bluetooth w telefonie zainstaluje nasz znajomy aplikację która będzie nam przesyłała esemesy wysyłane oraz odebrane.
Gdy dysponujemy wiedzą oraz odpowiednimi urządzeniami jesteśmy w stanie podsłuchiwać każdą formę rozmów
Zna ktoś może jeszcze jakieś techniki podsłuchu?

UPDATE:

Malutkie urządzenie a nadajnik na dość sporą odległość…

Steps to setup VNC Server at Linux:

1. Install VNC Server (the name of the program might be different):
   1. Fedora (RPM): yum install vnc-server
   2. Ubuntu (DEB): sudo apt-get install vnc4server
2. After install, start VNC Server(it will ask you to enter a password):
   vncserver :1
3. Then stop VNC Server:
   vncserver -kill :1
4. Edit ~/.vnc/xstartup (it will not appear if you didn’t start VNC Server once). Uncomment the following 2 lines  to enable the Windows X in VNC Server (the lines might be different):
   # unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

5. Start again VNC Server:
   vncserver :1
6. In another machine, use your favorite VNC Client Program to access VNC Server:
   SERVER_IP:DISPLAY
   Display is the number after the colon you set at VNC Server. For example:
   192.168.1.33:1

1. Check that the VNC Server is Installed

# pkg info SUNWxvnc
system SUNWxvnc X11/VNC server

2. Add this line to /etc/services
vnc-server 5900/tcp # Xvnc

3. Configure /etc/X11/gdm/custom.conf file with lines
[xdmcp]
Enable=true
[security]
DisallowTCP=false
AllowRoot=true
AllowRemoteRoot=true


4. Enable the Services
# svcadm enable xvnc-inetd# svcs xvnc-inetd

5. Connect to the Display with a VNC Client