full-disclosure - Using Google Desktop Search for remote system monitoring

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1105272122.4602.6.camel@localhost.localdomain>
From: barrie at reboot-robot.net (Barrie Dempster)
Subject: Using Google Desktop Search for remote
	system monitoring

On Sat, 2005-01-08 at 17:51 -0500, Abe Usher wrote:
<snip>
> If you are interested in trying "desktop" search remotely, check out my
> write up at:
> http://www.sharp-ideas.net/

That isn't entirely remote from what I can see. You need to know the
salt value before you can find the page, you'd have to gain that value
locally each time in order to access the page remotely. Unless you find
out where it's stored and pipe that over the connection.

You could however code a small program to run on the google desktop
machine which both monitors the google desktop and opens a socket for
remote use, As it stands the  method you use isn't entirely useful other
than showing that you can redirect a loopback port to a network
accessible port which I'm sure we are all aware off.

Are you going to take this further or was it like you said just for
fun ?

With Regards..
Barrie Dempster (zeedo) - Fortiter et Strenue

  http://www.bsrf.org.uk

[ gpg --recv-keys --keyserver www.keyserver.net 0x96025FD0 ]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050109/a0b0d374/attachment.bin