Closed GoogleCodeExporter closed 8 years ago
This bug is specifically related to cleanMonitor routine. For this moment,
marching forward to finish the end to end communication. Hopefully will get a
chance to fix it before Tuesday 2pm,
ravi.
Original comment by ravt...@gmail.com
on 28 Oct 2012 at 9:10
When I try to kill a monitor, for some reason, the process that is being
killed, looks like, it goes into a recursive loop.
This is related to some signal handling. Still debugging.
Want to work out the communication with Android SSL-client and will return to
this bug,
ravi.
Original comment by ravt...@gmail.com
on 29 Oct 2012 at 2:15
Original comment by ravt...@gmail.com
on 29 Oct 2012 at 2:15
Fixed killing the mis-behaving monitor. The problem is in restarting it,
ravi.
Original comment by ravt...@gmail.com
on 30 Oct 2012 at 1:13
Original comment by heyyoul...@gmail.com
on 30 Oct 2012 at 2:32
Restarting a monitor is a security risk. It gives the hacker to put a
malicious program and run it. Don't give that opportunity.
If a monitor misbehaves, it does. Sure, there is security risk here too. But
giving hacker the ability to run malicious program at ease, in particular like
PERL program of socketmon, procmon is dangerous.
Original comment by ravt...@gmail.com
on 10 Nov 2012 at 5:48
Issue 57 has been merged into this issue.
Original comment by ravt...@gmail.com
on 10 Nov 2012 at 5:50
Fixed it,
ravi.
r746
Original comment by ravt...@gmail.com
on 12 Nov 2012 at 2:10
Verified with unit testing
Original comment by tbrt....@gmail.com
on 9 Dec 2012 at 9:24
Original issue reported on code.google.com by
ravt...@gmail.com
on 28 Oct 2012 at 7:21