morgan
/
blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix

This commit is contained in:
Morgan 2024-04-01 16:49:58 +09:00
parent bbcab11c43
commit fcb37abd61
No known key found for this signature in database
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/2024-03-26-playing-with-snu-eam.md
View File

@ -1,6 +1,6 @@
--- ---
title: "Playing with SNU Attendance System" 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 slug: playing-with-snu-eam
description: "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. `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. 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.