My Tor relay is working as an Exit, but it is configured with ExitPolicy reject *:*.

Hanswurst is the name of my relay.

Arm is giving me the warning, that the torrc differs from what tor's using.

When I perform a SIGHUP to reload the torrc, my relay isn't an exit any longer.

Can i trust the arm connection list?

I use an RaspberryPi to route all wireless connections through the Tor network. Acting as an Tor client only works really well.

Log notice file /var/log/tor/notices.log
#DataDirectory /var/tor
VirtualAddrNetwork 10.192.0.0/10
AutomapHostsSuffixes .onion,.exit
AutomapHostsOnResolve 1
Exitpolicy reject *:*
StrictNodes 1
ExitNodes $E0C2C5223F6C219C5D41F57FFDF65661A36BCDA6, ...
TransPort 9040                      <--------------- Line 23
TransListenAddress 192.168.42.1
AvoidDiskWrites 1
DNSPort 53
DNSListenAddress 192.168.42.1
ControlPort 9051
ControlListenAddress 127.0.0.1:9051
HashedControlPassword 16:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
DisableDebuggerAttachment 0

##Relaystuff
ORPort 9000
Nickname Hanswurst
RelayBandwidthRate 512 KB
RelayBandwidthBurst 1024 KB
ContactInfo sauerbraten[a t]privatdemail{dot]net

I added the ExitPolicy parameter in the default config too, but it made no difference. Every time i start the Tor service, my relay works as an exit. When i reload the config it isn't an exit any longer..

Is my torrc causing that behavior?

Edit: I added the option DisableDebuggerAttachement 0 and got that list. The connections look kinda scary for being a relay..