Termi, read the brief in Pundit's thread hapo juu.
http://www.nipate.org/index.php?topic=5039.0
The narrative is not good. Raila should fire whoever came up with this angle. It's a celebration of ignorance on a different scale.
They should focus on the Forms 34. That is where the real problem is and has already been addressed by the courts.
So basically the insinuation of msando logins passwords was complete nonsense. Seriously this was quite irresponsible and unnecessary .
I didn't quite get to looking
thoroughly at the logs, having been discouraged by the level of illiteracy(the key claims are made on the basis of this lack of understanding). Optimization settings for instance are assigned ominous purposes which they don't serve.
For example
At the same time, they set the Date Correlation Optimization to off. In doing this, they effectively disabled the system from detecting date and time
This option has nothing to do with detecting date and time(whatever that means). It's an optimization option to improve the performance of table joins that use dates as keys.
However, if the logs are genuine and not tampered with, there was indeed a failed attempt to log in using first
Chebukati and later on
msando logins from the database server itself. That in itself can raise questions.
08/08/2017 09:05:23,Logon,Unknown,Login failed for user 'msando'.
Reason: The password of the account must be changed. [CLIENT: <local machine>]
08/08/2017 09:05:23,Logon,Unknown,Error: 18488<c/> Severity: 14<c/> State: 1.
08/08/2017 04:46:11,Logon,Unknown,Login failed for user 'Chebukati'.
Reason: The password of the account must be changed. [CLIENT: <local machine>]
It looks bad to a casual observer. But to make anymore of this you have to know for a fact that
1) the logs are genuine
2) there are in fact such users
If they can make up parts of it, I really don't consider the entire compendium of documents reliable.