On 28/10/11 19:30, Dom Latter wrote:
Which got me thinking that t-mobile must be
*monitoring* or even
*proxying* the connection and chopping it off once it threatens
to become encrypted and unmonitorable.
With that in mind a bit of googling led to:
http://support.t-mobile.co.uk/help-and-support/index?page=support&cat=M…
which I think explains it.
Why do people bother with starttls, bound to be open to all sorts of man
in the middle attacks, this is why nobody ever bothered using it for
escalating HTTP connections.
Use sstmp on port 465...
There is only one mode and it's encrypted...