Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any Plan for Code Audit #2310

Closed
sr093906 opened this issue Feb 8, 2023 · 7 comments
Closed

Any Plan for Code Audit #2310

sr093906 opened this issue Feb 8, 2023 · 7 comments
Labels

Comments

@sr093906
Copy link

sr093906 commented Feb 8, 2023

As a key project helping people bypass network restriction, do you have any plan to conduct professional code audit to ensure security of user and project itself?

Maybe cure53?

https://cure53.de/

For audit fee, you can raise money from users and even proxy services relying on v2ray-core. It is a win-win in my opinion,

@cross-hello
Copy link

cross-hello commented Feb 8, 2023 via email

@AkinoKaede
Copy link
Contributor

It's a great idea, but it's hard to raise the money needed to audit the code. As an open source project, V2Ray relies on unpaid audits by developers and researchers.

@sr093906
Copy link
Author

sr093906 commented Feb 9, 2023

It is not an impossible task.

With a big user base, financial contribution can be expected if you ask, and code auditor may offer service at discounted price for public-interest project.

I am cognizant of the difficulties though.It will be hard without trusted major sponsors and even risky since attackers may reveal developers' real identities via transaction records.

@xiaokangwang
Copy link
Contributor

Based on information from https://www.coreinfrastructure.org/programs/audit-program/, a cost review cost anywhere from 15K ~ 38K for a code base at V2Ray's scale, and the cost would be significantly harder if dependency of V2Ray are included in the review.

We don't currently have any plan for a fundraising at that scale(the corejs author claim to receive as little as $400 a month in the readme, after extensive funding effort). So, to answer your question, we won't be able to afford it even with fundraising. (And it is not like any of the author can just absorb this cost like other minor expense V2Ray have.)

That being said, we are more than happy if there is someone run a code audit of V2Ray, at their own cost, and share their finding with us.

If anyone are still determined to get V2Ray a code audit, there is a Red Team Lab from USAGM's OTF that claim to provide code audit at their own cost. If someone is willing to contact them and negotiate a code audit, at their own cost, please comment in the thread.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Jun 17, 2023
@sr093906
Copy link
Author

making comment to keep the issue open

@github-actions github-actions bot removed the Stale label Jun 18, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Oct 17, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants