Thursday, 27 March 2008

Privoxy: Submitting Javascript-Forms

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We just found a post on the onionforum (tor required) with a nice filter for privoxy.

It adds a submit-button to forms that are usually submitted via javascript and makes them usable for javascript-disabled browsers.

Add this to your .filter -file

FILTER: unhide
s@(<input type="?)hidden("?[^>]+name="?([^" >]+)"?)@$1text$2 style="background-color:RoyalBlue" title="$3"@gis
s@<input type="submit" value="s" style="background-color:RoyalBlue"></form>@<input type="submit" value="s" style="background-color:RoyalBlue"><input type="submit" value="s" style="background-color:RoyalBlue"></form>@gis
s@display: ?none@background-color:CornflowerBlue@gis
s@(<[^>]*?)disabled(="disabled")?@$1@gis


...and the following to your .action -file:

{ +filter{unhide} }
/

..or to enable this only for specific sites:


{ +filter{unhide} }
.evilshare.com/
.example.com


If it does not work, you can try:

{ +filter{unhide} +prevent-compression }

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFH64tjLAZ+Vq4hPgARAnh7AJ9AM140LvxN7PYYiC3q+gREN4TrPgCfSrnQ
eZUGPh2diU98pDmXLAfC7q0=
=Rq8g
-----END PGP SIGNATURE-----

Wednesday, 13 February 2008

faster ssh/scp on SMP/multi-core systems

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A nice paper just popped up on
the tor-mailing list.


Abstract
SCP and the underlying SSH2 protocol implementation in OpenSSH is network performance limited by statically defined internal flow control buffers. These buffers often end up acting as a bottleneck for network throughput of SCP, especially on long and high bandwith network links. Modifying the ssh code to allow the buffers to be defined at run time eliminates this bottleneck. We have created a patch that will remove the bottlenecks in OpenSSH and is fully interoperable with other servers and clients. In addition HPN clients will be able to download faster from non HPN servers, and HPN servers will be able to receive uploads faster from non HPN clients. However, the host receiving the data must have a properly tuned TCP/IP stack. Please refer to this tuning page for more information.

The amount of improvement any specific user will see is dependent on a number of issues. Transfer rates cannot exceed the capacity of the network nor the throughput of the I/O subsystem including the disk and memory speed. The improvement will also be highly influenced by the capacity of the processor to perform the encryption and decryption. Less computational expensive ciphers will often provide better throughput than more complex ciphers.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHs/FVLAZ+Vq4hPgARAt3SAKCe3ntK729GBG3uAY6PMh6Xa9WjXgCg1Swr
vv3DTUO3G+/c4w7utqmuCuI=
=pzqX
-----END PGP SIGNATURE-----

Thursday, 31 January 2008

getting anonymous gpg-keys signed


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


GPG is a fine thing with it's web of trust.
But the probleme here being...a web of trust is not anonymous.
There is no identity to prove to get a key sign if you want to
be anonymous.

One nice service here is the
PGP Global Directory.
It does only checks that one of the email-adresses in the key indeed works.
Just like a double-opt-in.

Another one is the robotCA, where you send an email to robotca AT signedtimestamp DOT org with the subject "sign key: your key id" (e.g. "sign key: AE213E00") and it will load that key from a keyserver and send a signed copy to the email-adresses in it.

But at least that's something that can be done.
Verify that the key-owner can recevive at that that address without sending a message yourself.
(Like, if that key is to be used outside of an email-context.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHuZdjLAZ+Vq4hPgARAoJUAJ975yR30c11Tj0PI0oOLMmmkgm2KQCdFTl6
dq9/QQi+jM396gv8XAFmurQ=
=y1vL
-----END PGP SIGNATURE-----

Tuesday, 18 December 2007

possibly backdoored random-number-generator added with Vista-SP1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



As reported by Bruce Schneier (A very well known cryptoanalyst),
Microsoft has added the Dual_ElipticCurve- PseudoRandomNumberGenerator to Windows Vista.

Exactly this PRNG has is suspected to have a backdoor added to it,

The Overview of Windows Vista Service Pack 1 states: "The Dual Elliptical Curve (Dual EC) PRNG from SP 800-90 is also available for customers who prefer to use it."





- - From Did NSA Put a Secret Backdoor in New Encryption Standard? By Bruce Schneier, Wired News, November 15, 2007:

In an informal presentation (.pdf) at the CRYPTO 2007 conference in August, Dan Shumow and Niels Ferguson showed that the algorithm contains a weakness that can only be described a backdoor.

This is how it works: There are a bunch of constants -- fixed numbers -- in the standard used to define the algorithm's elliptic curve. These constants are listed in Appendix A of the NIST publication, but nowhere is it explained where they came from.

What Shumow and Ferguson showed is that these numbers have a relationship with a second, secret set of numbers that can act as a kind of skeleton key. If you know the secret numbers, you can predict the output of the random-number generator after collecting just 32 bytes of its output. To put that in real terms, you only need to monitor one TLS internet encryption connection in order to crack the security of that protocol. If you know the secret numbers, you can completely break any instantiation of Dual_EC_DRBG.

The researchers don't know what the secret numbers are. But because of the way the algorithm works, the person who produced the constants might know; he had the mathematical opportunity to produce the constants and the secret numbers in tandem.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHiyK4LAZ+Vq4hPgARAiEmAKDT3SXjRrImTxUYwheeOJl+shzsOgCeJf7j
O/5jZwEnPpMxOu7jVQ3maHo=
=DF2y
-----END PGP SIGNATURE-----

Combine webmail and GPG using the FireGPG-Extension for Firefox

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So, you are using TOR to access a gmail- or other webmail-account?

You can use gpg just fine for any email-program but....with webmail there is no such email.

Enter FireGPG.

With this extension you get a context-menu where you can sign, encrypt, decrypt and verify any text you select.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6XhLAZ+Vq4hPgARApUcAKDLT8APB29NyIgK0h+vavL8faNqaACgo7H2
XJvMEAQCwnnRidzuaDZOwRk=
=LxcJ
-----END PGP SIGNATURE-----

Monday, 17 December 2007

Tor and privoxy had been ported to iphone

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

from cjacker huang on or-dev:

I just ported libevent, tor-0.1.2.18 and privoxy to iphone 1.1.1 fw.
and finished a iPhone app named iTor.app.
...
It works pretty good on iphone. also I tested it with privoxy on PC
and tor on iphone.

for more infomation and source.
http://www.linux-ren.org/modules/everestblog/?p=161



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6e5LAZ+Vq4hPgARAroOAKC+wNkt1w4d7d2ZFFbo74t+Ao7n/QCfWt4J
PFJftkVmwY5w9N9MeFfbGsM=
=Ocq5
-----END PGP SIGNATURE-----

Saturday, 15 December 2007

european data-retention - what does it mean to you, Mr. Operator?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(links given by an austrian informant.)

All over europe people offering anonymity-services are forced to log within the next 13 month.

A german tor-operator now published in his blog under the title ""We are fucked individually!"" the commented, relevant parts of the laws as applicable to tor-operators.

On the german tor-talk mailing-list he gave the following numbers for estimated storage-space required for logging after doing real-world experimentation of that toppic.

Server Traffic: 2.000 KB/s average
logs for 1 week: 200 GByte
logs for 1 week after removing irrelevant content: 120 GByte
after compression and encryption: 20 GByte
sum for 26 weeks (6 month): 500 GByte average
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6eyLAZ+Vq4hPgARAtgsAKCk5tQF7EJakP82MlSqG+H0TY+VvwCeOSEE
/ryHIw2Oi5y+QVCabujYKNg=
=/HZL
-----END PGP SIGNATURE-----

Wednesday, 12 December 2007

Hundreds searched illegally at Gatwick

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

from: The Guardian

Louise Radnofsky and agencies
Wednesday December 12, 2007
Guardian Unlimited

Hundreds of passengers at Gatwick airport have been subjected to illegal police "stop and searches", the Home Office admitted in a written statement today.

Sussex police made a paperwork error when they applied for special permission to stop people without "reasonable grounds" that a crime is in progress, said the security minister, Tony McNulty.

The 259 people stopped and searched by Sussex police during three weeks in September will receive apologies, McNulty said, adding that Home Office officials were reviewing the paperwork connected with stop and search tactics under the Terrorism Act 2000 to check for more mistakes.

"No arrests occurred as a result of these stop and searches," he said.

"However, Sussex police will shortly be writing to all of the individuals concerned to apologise.

"All steps have now been taken to ensure ... that such regrettable and serious omissions do not occur again."

A similar mistake was found to have happened in 2003, he said.

A Sussex police spokesman said the force accepted full responsibility for the blunder.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6esLAZ+Vq4hPgARAvGWAJ0WIcYylTq+R/vcqIfPWhDOcLaEjwCfZTo7
POA7bFBHq32STco4Gh5EJys=
=5MAS
-----END PGP SIGNATURE-----

Friday, 7 December 2007

German Privacy Foundation cares for tor-admins and politicians

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Our german informant has been quite busy lately. Here is a complete article from him:

As mentioned on heise news, the newly founded Privacy Foundation is to inform police-personell, courts, tor-admins and politicians alike about privacy-techniques like tor.
This step was found to be needed because of raids on tor-admins lately by uninformed policy that did not know or believe that there where no logs to be found by such a raid.
The foundation is also to help journalists not misrepresent tor and other services to the public.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6fGLAZ+Vq4hPgARAtG0AKDLSUlAgyEgcwe4V0Ljf137r66n4ACeMXXs
xxob1qHW886KT5ekXV7ds80=
=YMPy
-----END PGP SIGNATURE-----

Sunday, 2 December 2007

Freenode forced to block tor-clients temporarily

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As stated in the staff blog freenode was forced to block tor-clients because a company named "B & C Advanced Solutions" was violating their policies by creating and publishing chat-logs covertly by bot connecting through the tor-network.
Freenode states that they where unable to identify the boty any other way.

Access via gpg-tor is supposed to be unaffected.

other blog-posts:
irseek: open letter to IRC-operators

techcrunch: Will IRSeeK Have A Chilling Effect on IRC Chat?

IrSeek-page on vorratsdatenspeicherung.de (in english) (provided by a german informant)

geekosphere.org (provided by a german informant)

laxu (provided by a german informant)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6enLAZ+Vq4hPgARArKBAKC2O28RffvTbRG+akMzFT3hld4EMwCfbyic
e5pQbFR6Bij5uvKZ7EOMmog=
=dfqP
-----END PGP SIGNATURE-----

Friday, 30 November 2007

Jury Trial, Jury Nullification

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is an ongoing discussion on the OnionRouter-Talk mailing list that may be of interest to readers familar with the jury-system in the United Stated of (northern) America.

Apperently there was a 1996-case in the US where a jury-member got a sentence because of informing the other jury-members of (truthfully) a right they had. Also interesting to this topic may be the Fija-organisation.

Note that we did not check the facts presented here to be true. Thus don't trust a site just because "it's written" and don't trust us for that matter.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6ebLAZ+Vq4hPgARAkbGAKDLd4KDVvYykW/JIIxodXB1qy7WQgCfRCbF
tAN58vYa98vIpU4Bvvid4Cg=
=QsrD
-----END PGP SIGNATURE-----

Thursday, 29 November 2007

password need not be produced in USofA-court

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

the source(pdf)

A US-District-Court issued a ruling that a canadian need not release the password for his pgp-drive because that is a thought and he has the right to remain silent about his thoughts.
Formerly a password was often seen as a key by the accusers that could be forced to be produced.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6eVLAZ+Vq4hPgARAmbZAKCLC9tuRWuNC5cfGk+RgCC7g4mhPwCbBR9H
KL76qxeXZ0AfpVi3rvirCIM=
=6ewt
-----END PGP SIGNATURE-----

Wednesday, 28 November 2007

setting up your own search-enging for torland

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We stumbled over YaCy as a distributed search-enging. It's quite a nice thing
but being distributed unless changed it just starts connecting to it's non-tor-peers
and index the web.
But...you can configure it to be part of the network of CaCy-Servers on tor and help
index torland. As a side-effect you get a local search-index that is allways reachable
without lag.

Parts needed:

Java 1.4.x
some free ram and disk
some free bandwidth

english setup-instructions

german setup-instructions

short YaCy+ot howto on the hidden wiki

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6eJLAZ+Vq4hPgARAmxVAJ9tfw+DWJ2Vo+rx1uDf6LxJGo7jPgCfalQV
BhKl2PEIR9n/PgspJxuFdA0=
=Ir1d
-----END PGP SIGNATURE-----

newsflash: Google hands over IP address of anonymous blogger

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

from: globes.co.il:

(shortened)

In an unprecedented move, Google has agreed to supply the IP address of an Israeli blogger who
used "Google Blogger" for a blog in which he slandered Shaarei Tikva council members running for
reelection...

The council members asked Google for the blogger's name.
They reached a settlement with the company on the basis of an Israeli ruling on the subject.
The settlement stipulates that 72 hours before a hearing ...the council members would leave the
blogger a message on his blog summoning him to the hearing, or else his IP address would be
handed over. The notice would invite the blogger to disclose his identity, participate in the
hearing, or oppose the disclosure of his identity by filing a motion as "anonymous".
...
Google initially said that disclosing the blogger's identity violated rulings on the balance
between freedom of expression and a person's right to his reputation.

However, in a pre-ruling, Judge Oren Schwartz said that the blog's content raised suspicions of
criminal conduct, and Google took the hint.
...
In line with Judge Schwartz's ruling, Google and the councilmen reached a settlement in their
dispute. Following the 72 hour period, Google was ordered to hand over the IP address to the
court....



note: this is not about us. "anonymous" is a fairly...common name nowadays. ;)


We have been given the following links with good articles about the case in major german online-publications.
coverage on lawblog and coverage on heise.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6eBLAZ+Vq4hPgARAkYyAJ9e8yC/ibAkBe638Dk/zkxJll6ifgCgmj5W
j16gdMwdUnGf2jRar/I/GJg=
=8KO8
-----END PGP SIGNATURE-----

providing ssh as a tor-hidden-service

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

step 1: create the service

create the service-directory

mkdir /var/lib/tor/hidden_service
mkdir /var/lib/tor/hidden_service/ssh
chown tor /var/lib/tor/hidden_service/ssh (may be "debian-tor" for debian-users)


now add to your /etc/tor/torrc

HiddenServiceDir /var/lib/tor/hidden_service/ssh
HiddenServicePort 22 127.0.0.1:22


step 1a: reload tor and check that it works

/etc/init.d/tor reload
tail /var/log/tor/log

now

cat /var/lib/tor/hidden_service/ssh/hostname

will give you the .onion-address to use

step 2: configure the client

first, download connect.c from latency.net to allo ssh to connect to a socks-proxy.
compile it with

gcc connect.c -o /etc/ssh/connect

and in /etc/ssh/ssh_config
add the following configuration for all .onion-addresses


# use /etc/ssh/connect to use tor to connect to ssh in torland
Host *.onion
ProxyCommand /etc/ssh/connect -S localhost:9050 %h %p



done. Now you can do a "ssh fox@XYZ.onion" every time your local tor-server is running.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6d7LAZ+Vq4hPgARAiDUAJ4zj99ZM8vwwNnEhi6UeR9WbUNTEACgtSgb
Br17oxsyxfwoTwLxL+rr2zg=
=rQE0
-----END PGP SIGNATURE-----

"anonymous living"-blog

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We just discovered the anonymous living -blog.
You may want to have a look there. It looks quite good and lively!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6dxLAZ+Vq4hPgARAiUrAJ9TQwPz1cgYqPLVloK6pxwjxoHExACdGOE+
LeFIIZHSM68H8b+dMI+n2q4=
=NWhE
-----END PGP SIGNATURE-----

Tuesday, 27 November 2007

Tor 0.2.0.12-alpha fixes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Today Tor 0.2.0.12-alpha was released, fixing among other things "a giant memory-leak".
Here is the Freshmeat announcement.


This release fixes some build problems with the previous snapshot. It also includes a more
secure-by-default exit policy for relays, fixes an enormous memory leak for exit relays, and fixes
another bug where servers were falling out of the directory list.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6dfLAZ+Vq4hPgARApnLAJ4r8HWmehEyrQGISTkkdooJI1llKACdH0cB
YDoEyRbiXy4x1cv65qD65is=
=U0Uj
-----END PGP SIGNATURE-----

masked.name

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We recently discovered a nice service we wanted you to know about:
masked.name

You can register here(using tor) and then use a mail, im, irc, ftp in torland and have a public (as in outside torland and on the normal internet) blog on NAME.masked.name.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6dHLAZ+Vq4hPgARAk8lAJ47fJuUCo1LbyCN2ZiZGOYOJKbViQCfYl37
VHqEsP6AopDM9r9ZleHak4w=
=gG+3
-----END PGP SIGNATURE-----

Saturday, 24 November 2007

small personal fight in torland

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It looks like a small fight has started in torland.
Matt and Jamon are fighting over "who provides the best hidden services".

Well, we are allways pro-competition so let us see how much improvement in quality and quantity of hidden services we will end up with.

Matt is operating

Jamon operates

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6ckLAZ+Vq4hPgARAu44AJ9Zt46BW5l59y4YjrtbbRbvtxI/QgCfdq0D
cch04g3ri3/GTx3vLYZcbak=
=HIw8
-----END PGP SIGNATURE-----

Tuesday, 20 November 2007

transocks - transparently torify all tcp connections on the router

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

transocks from Mike Fisk looks pretty cool.

usage:

#!/bin/sh

# start transocks
/usr/local/sbin/transocks -p 1211

LOCAL_NET=192.168.0.0/16

# create a new chain 'SOCKSIFY' for it to simplify management
iptables -t nat -X SOCKSIFY
iptables -t nat -N SOCKSIFY

# exceptions that are not to be run through tor
iptables -t nat -A SOCKSIFY -o lo -j RETURN
iptables -t nat -A SOCKSIFY --dst 127.0.0.1 -j RETURN
iptables -t nat -A SOCKSIFY --dst $LOCAL_NET -j RETURN

# avoid feedback loops
iptables -t nat -A SOCKSIFY -m owner --cmd-owner transocks -j RETURN

# log every new connection in the SOCKSIFY-chain
iptables -t nat -A SOCKSIFY -j LOG -p tcp --syn --log-level info \
- --log-prefix "SOCKSify "

# send tcp-connections in the SOCKSIFY-chain to transocks
iptables -t nat -A SOCKSIFY -p tcp -j REDIRECT --to-port 1211

# Socksify traffic leaving this host:
iptables -t nat -A OUTPUT -p tcp --syn -j SOCKSIFY

# Socksify traffic routing through this host:
iptables -t nat -A PREROUTING -p tcp -s $LOCAL_NET --syn -j SOCKSIFY

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFHZ6cdLAZ+Vq4hPgARAjDTAKCRkUEB5+nz54xId38XWi2RXKckeQCffJ8i
qKTGU+Fk/w56t+UwiGFd1CQ=
=tq8N
-----END PGP SIGNATURE-----