Make exceptions easier to translate to error codes

Avoid throwing base Botan::Exception type, as it is difficult to
determine what the error is in that case.

Add Exception::error_code and Exception::error_type which allows
(for error code) more information about the error and (for error type)
allows knowing the error type without requiring a sequence of catches.

See GH #1742

1 files changed, 2 insertions, 2 deletions

diff --git a/src/lib/tls/sessions_sql/tls_session_manager_sql.cpp b/src/lib/tls/sessions_sql/tls_session_manager_sql.cpp
index 45b3059f5..1959db266 100644
--- a/src/lib/tls/sessions_sql/tls_session_manager_sql.cpp
+++ b/src/lib/tls/sessions_sql/tls_session_manager_sql.cpp
@@ -69,14 +69,14 @@ Session_Manager_SQL::Session_Manager_SQL(std::shared_ptr<SQL_Database> db,
          m_session_key.assign(x.begin() + 2, x.end());
 
          if(check_val_created != check_val_db)
-            throw Exception("Session database password not valid");
+            throw Invalid_Argument("Session database password not valid");
          }
       }
    else
       {
       // maybe just zap the salts + sessions tables in this case?
       if(salts != 0)
-         throw Exception("Seemingly corrupted database, multiple salts found");
+         throw Internal_Error("Seemingly corrupted TLS session db, multiple salts found");
 
       // new database case