altcha 2.0.0.beta1 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 86a8015b761012e385bf6b5756e3cc06ab6e0918efebcdc7fc244e029c200e69
4
- data.tar.gz: 187c01c7e93e15676c755ec9105955447c048c2e2c0249a270a44e735ea41666
3
+ metadata.gz: 614821123caf617aa6fa7cb26f4f9accedb5147d7e8f96ad51e6b785ac769029
4
+ data.tar.gz: d1fb7cf2d8599ae569c0b15973e0af96315e45863733ad97b7013dd2e982b7ef
5
5
  SHA512:
6
- metadata.gz: 98e5fd75d6640ac91149c917bbc45e6bebe02fa03f1b0d0a201382675579ec8d6e2d8dcc85d17ef608833972b44dfc81df07e7f6f7964ce9da25cb1c47ef1530
7
- data.tar.gz: 6daf6a061f5340a93c920ab6e2973b49979b77031c548845ad9a78fc363aed96e1f43e7de561b2f924b4401f5949c4356c1af1cda66a3e44d9ce693d23d1dc18
6
+ metadata.gz: b09b0f6917754cfa1a2db31d8bbe35a505cf2e8a81f948079ea7460a90d6cebfc9f16c576ed598fdd8079568821e559c5b91bb479de65f634347bcf39b513a31
7
+ data.tar.gz: 8fdc4d5ae63d8f17843f20c55f4343bcf310ef80da3938dc437f9f20d4081b2da8984309e6faf556bb14b66dfca3db667111f19946068c5c493fc881a7bc2c1e
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: Bug Report
3
+ about: Create a report to help us improve ALTCHA.
4
+ title: "[BUG] "
5
+ labels: bug
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ ## 🛑 Important: Bug Reports Only
11
+ Please use this template **only for reporting bugs**.
12
+
13
+ ---
14
+
15
+ ### Description
16
+ A clear and concise description of the bug.
17
+
18
+ ### Environment Details
19
+ * **Library Version:** (e.g., v2.0.0)
20
+ * **Runtime Version:** (e.g., Node.js v20, Go 1.22, Python 3.11)
21
+ * **Framework (if applicable):** (e.g., Express, Gin, FastAPI)
22
+ * **OS:** (e.g., Linux, Docker/Alpine, Windows)
23
+
24
+ ### Reproduction Code
25
+ Please provide a minimal, self-contained code snippet that reproduces the issue.
26
+ > **Warning:** Do not include your `secret` or private keys here.
27
+
28
+ ```text
29
+ (Paste your implementation here)
30
+ ```
31
+
32
+ ### Error Logs & Stack Trace
33
+ Please paste the full error output or stack trace from your server logs:
34
+ ```text
35
+ (Paste logs here)
36
+ ```
37
+
38
+ ### Expected Behavior
39
+ What was the expected result of the validation or library call?
40
+
41
+ ### Additional Context
42
+ Is this happening with specific algorithms (e.g., Argon2, SHA-256) or under specific load conditions?
43
+
44
+ ---
45
+ **Note:** Issues without environment details or reproduction code may be closed.
@@ -0,0 +1,5 @@
1
+ blank_issues_enabled: false
2
+ contact_links:
3
+ - name: 📖 Documentation
4
+ url: https://altcha.org/docs/v2
5
+ about: Check the official docs before opening an issue.
data/CONTRIBUTING.md CHANGED
@@ -1,36 +1,15 @@
1
1
  # Contributing to ALTCHA
2
2
 
3
- We appreciate your contributions! To ensure a smooth and transparent collaboration, we've outlined the various ways you can contribute to ALTCHA:
3
+ In light of the rapidly evolving open-source landscape, specifically the emerging security challenges and complexities introduced by AI-generated code, we have made the decision to restrict all direct contributions to our codebase.
4
4
 
5
- - **Reporting a Bug**
6
- - **Discussing the Current State of the Code**
7
- - **Submitting a Fix**
8
- - **Proposing New Features**
9
- - **Becoming a Maintainer**
5
+ ### No External Pull Requests
10
6
 
11
- ## Development with GitHub
7
+ At this time, we do not accept external pull requests or code contributions. All changes, updates, and bug fixes must be authored and vetted exclusively by our internal team. This policy allows us to maintain strict oversight of our security posture and ensure the long-term integrity of the project.
12
8
 
13
- ALTCHA is hosted on GitHub, where you can find the codebase, track issues, and submit pull requests. Please familiarize yourself with GitHub for effective collaboration.
9
+ ### How to Provide Feedback
14
10
 
15
- ## Licensing Information
11
+ While we are not accepting code, your input is still incredibly valuable to us. We encourage you to share your thoughts, report bugs, or suggest new features through our official contact channels: [https://altcha.org/contact/](https://altcha.org/contact/)
16
12
 
17
- Any contributions you make will be subjected to the project's MIT software license. By submitting code changes, you agree to license your contributions under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the entire project. If you have any concerns regarding licensing, feel free to reach out to the maintainers.
13
+ ### Security Vulnerabilities
18
14
 
19
- ## Reporting Bugs Using GitHub's [Issues](https://github.com/altcha-org/altcha-lib-rb/issues)
20
-
21
- We track public bugs using GitHub issues. Reporting a bug is easy: simply [open a new issue](https://github.com/altcha-org/altcha-lib-rb/issues). Provide detailed information for effective bug resolution.
22
-
23
- ## Writing Effective Bug Reports
24
-
25
- Good bug reports include:
26
-
27
- - A quick summary and background of the issue
28
- - Steps to reproduce the problem
29
- - Be specific!
30
- - Include sample code if possible
31
- - Expected vs. actual outcomes
32
- - Additional notes, such as your hypotheses or unsuccessful attempts to resolve the issue
33
-
34
- ## License Agreement
35
-
36
- By contributing to ALTCHA, you agree that your contributions will be licensed under the project's MIT License. If you have any questions or concerns, please reach out to the maintainers.
15
+ If you believe you have discovered a security vulnerability, please follow our Security Policy: [https://altcha.org/security-policy/](https://altcha.org/security-policy/)
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- altcha (2.0.0.beta1)
4
+ altcha (2.0.0)
5
5
  base64
6
6
 
7
7
  GEM
data/examples/server.rb CHANGED
@@ -71,20 +71,10 @@ server.mount_proc '/challenge' do |req, res|
71
71
  next
72
72
  end
73
73
 
74
- # options = Altcha::V2::CreateChallengeOptions.new(
75
- # algorithm: 'PBKDF2/SHA-256',
76
- # cost: 5_000,
77
- # counter: SecureRandom.random_number(5_000..10_000),
78
- # expires_at: Time.now + 300, # 5 minutes
79
- # hmac_signature_secret: HMAC_SECRET,
80
- # hmac_key_signature_secret: HMAC_KEY_SECRET
81
- # )
82
-
83
74
  options = Altcha::V2::CreateChallengeOptions.new(
84
- algorithm: 'ARGON2ID',
85
- cost: 2,
86
- memory_cost: 65536,
87
- counter: 10,
75
+ algorithm: 'PBKDF2/SHA-256',
76
+ cost: 5_000,
77
+ counter: SecureRandom.random_number(5_000..10_000),
88
78
  expires_at: Time.now + 300, # 5 minutes
89
79
  hmac_signature_secret: HMAC_SECRET,
90
80
  hmac_key_signature_secret: HMAC_KEY_SECRET
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Altcha
4
- VERSION = '2.0.0.beta1'
4
+ VERSION = '2.0.0'
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: altcha
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.0.beta1
4
+ version: 2.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Daniel Regeci
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2026-04-04 00:00:00.000000000 Z
11
+ date: 2026-04-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: base64
@@ -72,6 +72,8 @@ executables: []
72
72
  extensions: []
73
73
  extra_rdoc_files: []
74
74
  files:
75
+ - ".github/ISSUE_TEMPLATE/bug_report.md"
76
+ - ".github/ISSUE_TEMPLATE/config.yml"
75
77
  - ".github/workflows/publish.yml"
76
78
  - ".gitignore"
77
79
  - ".rspec"