Not every crypt error is due to flushing data!

src/sbbs3/js_socket.c

@@ -92,7 +92,7 @@ static int do_cryptAttributeString(const CRYPT_CONTEXT session, CRYPT_ATTRIBUTE_
 
 #define GCES(status, pdata, estr, action) do {                                               \
 	int GCES_level;                                                                      \
-	get_crypt_error_string(status, pdata->session, &estr, "flushing data", &GCES_level); \
+	get_crypt_error_string(status, pdata->session, &estr, action, &GCES_level); \
 	if (estr) {                                                                          \
 		lprintf(GCES_level, "%04d %s", p->sock, estr);                               \
 		free_crypt_attrstr(estr);                                                                  \
@@ -101,7 +101,7 @@ static int do_cryptAttributeString(const CRYPT_CONTEXT session, CRYPT_ATTRIBUTE_
 
 #define GCESH(status, socket, handle, estr, action) do {                                     \
 	int GCESH_level;                                                                     \
-	get_crypt_error_string(status, handle, &estr, "flushing data", &GCESH_level);        \
+	get_crypt_error_string(status, handle, &estr, action, &GCESH_level);        \
 	if (estr) {                                                                          \
 		lprintf(GCESH_level, "%04d %s", socket, estr);                               \
 		free_crypt_attrstr(estr);                                                                  \