[GH-ISSUE #3153] Verify if Same Code From This Repo

gitea-mirror commented

2026-05-05 13:37:38 -06:00

Owner

Copy link

Originally created by @flikites on GitHub (Oct 29, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3153

Bug Description

A company by the name of "Proxidize" uploaded files manually into github on September 15th, 2022 that claims to use this exact implementation of a FRP server. You can see the credits of their project to confirm by visiting: https://github.com/proxidize/proxidize-android/blob/main/CREDITS

They bundled the "server" file in Binary form and have stated that I should cross reference the MD5 with the binary of your repo:

This is the MD5 hash for the file below: 2C9148CF7F7EF624AD3DA7A7B4CB8B7C

https://github.com/proxidize/proxidize-android/blob/main/server/server

They told me to do a check on the MD5 so that's what I am doing:

https://prnt.sc/WWgUvNx1-ehS

Would you be able to confirm that the MD5 above matches up with your code from this repo?

frpc Version

not available

frps Version

not available

System Architecture

not available

Configurations

Binary?

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @flikites on GitHub (Oct 29, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3153 ### Bug Description A company by the name of "Proxidize" uploaded files manually into github on September 15th, 2022 that claims to use this exact implementation of a FRP server. You can see the credits of their project to confirm by visiting: https://github.com/proxidize/proxidize-android/blob/main/CREDITS They bundled the "server" file in Binary form and have stated that I should cross reference the MD5 with the binary of your repo: This is the MD5 hash for the file below: 2C9148CF7F7EF624AD3DA7A7B4CB8B7C https://github.com/proxidize/proxidize-android/blob/main/server/server They told me to do a check on the MD5 so that's what I am doing: https://prnt.sc/WWgUvNx1-ehS Would you be able to confirm that the MD5 above matches up with your code from this repo? ### frpc Version not available ### frps Version not available ### System Architecture not available ### Configurations Binary? ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:37:38 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:37:42 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Oct 31, 2022):

In each release assets, there is a frp_sha256_checksums.txt file. You can check it by yourself.

@fatedier commented on GitHub (Oct 31, 2022): In each release assets, there is a `frp_sha256_checksums.txt` file. You can check it by yourself.

gitea-mirror commented

2026-05-05 13:37:42 -06:00

Author

Owner

Copy link

@flikites commented on GitHub (Oct 31, 2022):

Can you provide me a link to the file? I can't seem to find it in the repo.

@flikites commented on GitHub (Oct 31, 2022): Can you provide me a link to the file? I can't seem to find it in the repo.

gitea-mirror commented

2026-05-05 13:37:43 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Nov 1, 2022):

https://github.com/fatedier/frp/releases

@fatedier commented on GitHub (Nov 1, 2022): https://github.com/fatedier/frp/releases

gitea-mirror commented

2026-05-05 13:37:44 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 2, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Dec 2, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified