From 2625874ef8417a1594e8e92f3dea2b1ca8cf3634 Mon Sep 17 00:00:00 2001
From: deuce <>
Date: Tue, 27 Mar 2018 05:16:58 +0000
Subject: [PATCH] Some binkp software (Taurus) doesn't send an M_NUL VER at
all. Reported by bgdjr.
---
exec/binkit.js | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/exec/binkit.js b/exec/binkit.js
index 9081f23d74..11f5febe94 100644
--- a/exec/binkit.js
+++ b/exec/binkit.js
@@ -825,6 +825,8 @@ function mystic_broken_cram(bp)
var min;
var ver;
+ if (bp.remote_ver === undefined)
+ return false;
if (bp.remote_ver.substr(0, 7) !== 'Mystic/')
return false;
if (bp.wont_crypt)
@@ -909,7 +911,7 @@ function inbound_auth_cb(pwd, bp)
* non-working build. Hopefully, this is not the case, and this
* block can be removed.
*/
- if (bp.remote_ver === 'Mystic/1.12A39') {
+ if (bp.remote_ver !== undefined && bp.remote_ver === 'Mystic/1.12A39') {
log(LOG_INFO, "Checking Mystic pass...");
bp.cram.challenge += '\x00\x00\x00';
expected = bp.getCRAM('MD5', cpw);
--
GitLab