circumvent cascading exceptions

[CardboardBread]

when something like establish() is invoked and throws an exception, that exception is caught by keyCheck() and thrown from there into run() where it's finally displayed

since keyCheck can invoke four different methods with a host of exceptions (all which extend IOException) the intent of the exception beyond the stacktrace is lost.
especially since keyCheck() works independently of server/client architecture, the context behind what system is throwing an exception is also lost.