Opened 7 years ago
Last modified 6 years ago
#1320 new defect
BOB "quiet true" fail
Reported by: | kaos | Owned by: | sponge |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | apps/BOB | Version: | 0.9.13 |
Keywords: | error | Cc: | |
Parent Tickets: | Sensitive: | no |
Description
—- Short summary: —-
If I set quiet true (I also tried quiet True) when creating outgoing tunnels in BOB, and then connect to something that times out or generates some other error, BOB will - despite "quiet true" set - write an error message to the connecting socket.
I (successfully) entered the following commands into BOB:
setnick SOMENAME
setkeys SOME_VALID_KEYS
option inbound.length=3
option outbound.length=3
option inbound.lengthVariance=1
option outbound.lengthVariance=1
inhost 127.0.0.1
inport 12545
quiet true
start
Then connected to 127.0.0.1:12545 with socket S and wrote "duck.i2p\n".
And then read from the socket, assuming either socket error or real data, but got "ERROR java.net.. etc connection timed out"
—- My belief: —-
It should not write any error message, but instead just close the socket.
Thanks for an awesome project :D<3
Subtickets
Change History (1)
comment:1 Changed 6 years ago by
Keywords: | error added; quiet outgoing removed |
---|---|
Milestone: | 0.9.14 |