Session Start & Encryption NegotiationĪs a start point, log begins with Activating Router carrier, followed by encryption negotiation process where using AES-256 encryption algorithm for a symmetric key and RSA for key exchange. Let’s assume that remote access starts from Device A all the way to Device B.ġ. That aside, the file is automatically separated with the name of ‘TeamViewer#_OLD.log’ as soon as the size of original is over 1MB more or less. This tells us the program was upgraded from 14 to 15 at some point in the past. above, filename is containing version numbers, 14 or 15. ➔ Records detailed information of remote access & connections.Īll right, We have two logs illustrated in Fig 3. C:\Program Files(x86)\TeamViewer\TeamViewer#_Logfile.log (install path) ➔ Records general information of software operation.Ģ. %USERPROFILE%\AppData\Roaming\TeamViewer\TeamViewer#_Logfile.log Although they both have the same name, contents are distinct.ġ. Two log files with the exact same name are saved in different directories. TeamViewer#_Logfile.log is applied in LocalTime, UTC+9 in here South Korea. The two digits ‘#’ followed by ‘_Logfile.log’ indicates software version. Unlike the ‘connections_incoming.txt’, ‘TeamViewer#_Logfile.log’ has more rich information about remote access. We have more information coming right up, tips & details including IPv6 in part 2. In the previous post, we covered the basics of Teamviewer log analysis and confirmed that we have a lot more to delibrate from the basic log, ‘connections_incoming.txt’.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |