From fcb37abd61678d3bd3a0c3501daef6b71a26fce5 Mon Sep 17 00:00:00 2001 From: Morgan Date: Mon, 1 Apr 2024 16:49:58 +0900 Subject: [PATCH] Fix --- content/posts/2024-03-26-playing-with-snu-eam.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/2024-03-26-playing-with-snu-eam.md b/content/posts/2024-03-26-playing-with-snu-eam.md index 0f82272..93b4824 100644 --- a/content/posts/2024-03-26-playing-with-snu-eam.md +++ b/content/posts/2024-03-26-playing-with-snu-eam.md @@ -1,6 +1,6 @@ --- title: "Playing with SNU Attendance System" -date: 2024-03-30T18:00:48+09:00 +date: 2024-03-26T18:00:48+09:00 slug: playing-with-snu-eam description: "Playing with SNU EAM" --- @@ -331,4 +331,4 @@ I dont think there is a way to contain key in blackbox even for end user. User h `mitmproxy` done most important job in this case. Nowadays apps uses certificate pinning, but it was also useless with repackaging... So any problems is all sign verification and I think there is no way to perfectly do it. -Signature verifing is hard. Using Network is dangerous, and using internal logic can be also bypassed. I think only way to prevent this is in operating system, like in iOS it's much more hard to do this kind of job. \ No newline at end of file +Signature verifing is hard. Using Network is dangerous, and using internal logic can be also bypassed. I think only way to prevent this is in operating system, like in iOS it's much more hard to do this kind of job.