So i am working with the new impersonation-check system you added.
And i am not getting correct info for public keys,
Example: A node im testing it with has the following public key:
PYLO7kTPbJrEHJeUvBkrGLLp9jGMbEgJ0R3psixyAQM=
And yet in the impersonation-check, its key shows as:
"public_keys": ["3d82ceee44cf6c9ac41c9794bc192b18b2e9f6318c6c4809d11de9b22c720103"]
And looking at a node broadest payload you see its raw version
public_key: "=\202\316\356D\317l\232\304\034\227\224\274\031+\030\262\351\3661\214lH\t\321\035\351\262,r\001\003"
the actual key is not matching with what the impersonation-check shows. What is this hex/dec key MV stores if its not the actual key?
Just working this into our system to track keys and nodes and make sure all are legit.
Thanks
So i am working with the new impersonation-check system you added.
And i am not getting correct info for public keys,
Example: A node im testing it with has the following public key:
PYLO7kTPbJrEHJeUvBkrGLLp9jGMbEgJ0R3psixyAQM=
And yet in the impersonation-check, its key shows as:
"public_keys": ["3d82ceee44cf6c9ac41c9794bc192b18b2e9f6318c6c4809d11de9b22c720103"]
And looking at a node broadest payload you see its raw version
public_key: "=\202\316\356D\317l\232\304\034\227\224\274\031+\030\262\351\3661\214lH\t\321\035\351\262,r\001\003"
the actual key is not matching with what the impersonation-check shows. What is this hex/dec key MV stores if its not the actual key?
Just working this into our system to track keys and nodes and make sure all are legit.
Thanks
<!-- github-sync-id:3984698913 -->
We just track keys in a db table if we have more than one key then we report. The problem was that I was not trimming the table so found that some reports where always there... I added the fix to 3.0.7, thank you for your report.
We just track keys in a db table if we have more than one key then we report. The problem was that I was not trimming the table so found that some reports where always there... I added the fix to 3.0.7, thank you for your report.
<!-- github-comment-id:4493018787 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
So i am working with the new impersonation-check system you added.
And i am not getting correct info for public keys,
Example: A node im testing it with has the following public key:
PYLO7kTPbJrEHJeUvBkrGLLp9jGMbEgJ0R3psixyAQM=
And yet in the impersonation-check, its key shows as:
"public_keys": ["3d82ceee44cf6c9ac41c9794bc192b18b2e9f6318c6c4809d11de9b22c720103"]
And looking at a node broadest payload you see its raw version
public_key: "=\202\316\356D\317l\232\304\034\227\224\274\031+\030\262\351\3661\214lH\t\321\035\351\262,r\001\003"
the actual key is not matching with what the impersonation-check shows. What is this hex/dec key MV stores if its not the actual key?
Just working this into our system to track keys and nodes and make sure all are legit.
Thanks
We just track keys in a db table if we have more than one key then we report. The problem was that I was not trimming the table so found that some reports where always there... I added the fix to 3.0.7, thank you for your report.