jucrypt 0.1.0__tar.gz
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.
- jucrypt-0.1.0/LICENSE +201 -0
- jucrypt-0.1.0/PKG-INFO +333 -0
- jucrypt-0.1.0/README.md +317 -0
- jucrypt-0.1.0/jucrypt/__init__.py +4 -0
- jucrypt-0.1.0/jucrypt/story.py +209 -0
- jucrypt-0.1.0/jucrypt.egg-info/PKG-INFO +333 -0
- jucrypt-0.1.0/jucrypt.egg-info/SOURCES.txt +9 -0
- jucrypt-0.1.0/jucrypt.egg-info/dependency_links.txt +1 -0
- jucrypt-0.1.0/jucrypt.egg-info/top_level.txt +1 -0
- jucrypt-0.1.0/pyproject.toml +28 -0
- jucrypt-0.1.0/setup.cfg +4 -0
jucrypt-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 I., NABIL
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
jucrypt-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,333 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: jucrypt
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: JuCrypt is an experimental symmetric cipher where the encryption key is a piece of text you write — a story, a sentence, a memory. The longer and more unique your story, the stronger your encryption. (Experimental)
|
|
5
|
+
Author-email: "I., Nabil" <w3nabil@gmail.com>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Classifier: Development Status :: 3 - Alpha
|
|
8
|
+
Classifier: Intended Audience :: Developers
|
|
9
|
+
Classifier: Intended Audience :: Education
|
|
10
|
+
Classifier: Topic :: Security :: Cryptography
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Requires-Python: >=3.9
|
|
13
|
+
Description-Content-Type: text/markdown
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
Dynamic: license-file
|
|
16
|
+
|
|
17
|
+
# Ju's Story (STORY)
|
|
18
|
+
|
|
19
|
+
> **Your story is your key.**
|
|
20
|
+
> A story-key driven Substitution-Permutation Network cipher.
|
|
21
|
+
|
|
22
|
+
[](https://www.python.org/)
|
|
23
|
+
[](LICENSE)
|
|
24
|
+
[](https://pypi.org/project/jucrypt/)
|
|
25
|
+
[]()
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## What is STORY?
|
|
30
|
+
|
|
31
|
+
STORY (Ju's Story) is an experimental symmetric cipher where the **encryption key is a piece of text you write** — a story, a sentence, a memory. The longer and more unique your story, the stronger your encryption.
|
|
32
|
+
|
|
33
|
+
It is built on a **Substitution-Permutation Network (SPN)**, the same family of designs as AES. STORY is designed for **educational use, personal projects, and cryptography research**. It is not a replacement for AES-GCM or ChaCha20-Poly1305 in production systems. A research paper of this project is also available at [our personal website](https://w3nabil.com/archive/S-NAB-035.pdf) where we stated how we built this cipher.
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## ⚠️ Security Notice
|
|
38
|
+
|
|
39
|
+
> STORY is an **educational and research cipher**. It has **not** undergone formal cryptanalysis or peer review. Do not use it to protect sensitive personal data, financial records, medical information, or anything requiring compliance (HIPAA, GDPR, FIPS 140-2, etc.).
|
|
40
|
+
>
|
|
41
|
+
> For production security needs, use [AES-GCM](https://cryptography.io/en/latest/hazmat/primitives/aead/) or [ChaCha20-Poly1305](https://cryptography.io/en/latest/hazmat/primitives/aead/#cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305) via the `cryptography` library.
|
|
42
|
+
|
|
43
|
+
**Good uses for STORY:**
|
|
44
|
+
|
|
45
|
+
- Personal journals and diaries
|
|
46
|
+
- Learning how SPN ciphers work
|
|
47
|
+
- CTF challenges and cryptography coursework
|
|
48
|
+
- Hobbyist encryption experiments
|
|
49
|
+
- Prototyping novel key-derivation ideas
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## Installation
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
pip install jucrypt
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
Requires **Python 3.9 or higher**. No external dependencies — pure standard library. Unless you are testing. For testing please install the optional dependencies.
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Quick Start
|
|
64
|
+
|
|
65
|
+
### Encrypt and decrypt a message
|
|
66
|
+
|
|
67
|
+
```python
|
|
68
|
+
from jucrypt import story
|
|
69
|
+
|
|
70
|
+
mystory = "The first time I watched Ju Wenjun play chess, I knew she was extraordinary."
|
|
71
|
+
|
|
72
|
+
# Encrypt
|
|
73
|
+
ciphertext, nonce, tag = story.encrypt(b"Hello, Zerin!", mystory)
|
|
74
|
+
|
|
75
|
+
# Decrypt
|
|
76
|
+
plaintext = story.decrypt(ciphertext, mystory, nonce, tag)
|
|
77
|
+
print(plaintext) # b"Hello, Zerin!"
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
### Encrypt a file
|
|
81
|
+
|
|
82
|
+
```python
|
|
83
|
+
from jucrypt import story
|
|
84
|
+
|
|
85
|
+
mystory = "Anya Forger is not smart, she is just a copy cat master."
|
|
86
|
+
|
|
87
|
+
with open("diary.txt", "rb") as f:
|
|
88
|
+
data = f.read()
|
|
89
|
+
|
|
90
|
+
ciphertext, nonce, tag = story.encrypt(data, mystory)
|
|
91
|
+
|
|
92
|
+
# Save everything needed to decrypt later
|
|
93
|
+
with open("diary.story", "wb") as f:
|
|
94
|
+
f.write(nonce + tag + ciphertext) # prepend nonce and tag
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
### Decrypt a file
|
|
98
|
+
|
|
99
|
+
```python
|
|
100
|
+
from jucrypt import story
|
|
101
|
+
|
|
102
|
+
mystory = "Anya Forger is not smart, she is just a copy cat master."
|
|
103
|
+
|
|
104
|
+
with open("diary.story", "rb") as f:
|
|
105
|
+
raw = f.read()
|
|
106
|
+
|
|
107
|
+
nonce = raw[:8] # first 8 bytes
|
|
108
|
+
tag = raw[8:40] # next 32 bytes
|
|
109
|
+
ciphertext = raw[40:] # remainder
|
|
110
|
+
|
|
111
|
+
plaintext = story.decrypt(ciphertext, mystory, nonce, tag)
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## Command-Line Interface
|
|
117
|
+
|
|
118
|
+
Planned to introduce in future....
|
|
119
|
+
|
|
120
|
+
## API Reference
|
|
121
|
+
|
|
122
|
+
### `story.encrypt(plaintext, yourstory)`
|
|
123
|
+
|
|
124
|
+
Encrypts plaintext using the given story as the key.
|
|
125
|
+
|
|
126
|
+
```python
|
|
127
|
+
ciphertext, nonce, tag = story.encrypt(plaintext: bytes, story: str)
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
| Parameter | Type | Description |
|
|
131
|
+
|-----------|------|-------------|
|
|
132
|
+
| `plaintext` | `bytes` | The data to encrypt. Any length. |
|
|
133
|
+
| `story` | `str` | Your story — the encryption key. Any Unicode string. |
|
|
134
|
+
|
|
135
|
+
**Returns:** a 3-tuple of `(ciphertext, nonce, tag)` — all `bytes`.
|
|
136
|
+
|
|
137
|
+
| Return value | Size | Description |
|
|
138
|
+
|--------------|------|-------------|
|
|
139
|
+
| `ciphertext` | same as plaintext | Encrypted data |
|
|
140
|
+
| `nonce` | 12 bytes | Random value generated per encryption. Never reuse. |
|
|
141
|
+
| `tag` | 32 bytes | HMAC-SHA256 authentication tag |
|
|
142
|
+
|
|
143
|
+
> You must store **all three** values to decrypt later.
|
|
144
|
+
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
### `story.decrypt(ciphertext, yourstory, nonce, tag)`
|
|
148
|
+
|
|
149
|
+
Decrypts and authenticates a ciphertext.
|
|
150
|
+
|
|
151
|
+
```python
|
|
152
|
+
plaintext = story.decrypt(ciphertext: bytes, story: str, nonce: bytes, tag: bytes)
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
| Parameter | Type | Description |
|
|
156
|
+
|-----------|------|-------------|
|
|
157
|
+
| `ciphertext` | `bytes` | The encrypted data |
|
|
158
|
+
| `story` | `str` | The same story used to encrypt |
|
|
159
|
+
| `nonce` | `bytes` | The nonce returned by `encrypt()` |
|
|
160
|
+
| `tag` | `bytes` | The tag returned by `encrypt()` |
|
|
161
|
+
|
|
162
|
+
**Returns:** `bytes` — the original plaintext.
|
|
163
|
+
|
|
164
|
+
**Raises:** `ValueError` if the story is wrong or the ciphertext has been tampered with. Always handle this exception:
|
|
165
|
+
|
|
166
|
+
```python
|
|
167
|
+
try:
|
|
168
|
+
plaintext = story.decrypt(ciphertext, story, nonce, tag)
|
|
169
|
+
except ValueError:
|
|
170
|
+
print("Wrong story or corrupted ciphertext.")
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
### Internal methods (advanced use)
|
|
176
|
+
|
|
177
|
+
These are available for research and analysis but are not part of the stable public API.
|
|
178
|
+
|
|
179
|
+
| Method | Description |
|
|
180
|
+
|--------|-------------|
|
|
181
|
+
| `STORY._derive_master_key(story)` | Derives `(enc_key, mac_key)` from a story via HKDF |
|
|
182
|
+
| `STORY._derive_sbox(master)` | Derives a 256-byte S-box from key via Fisher-Yates |
|
|
183
|
+
| `STORY._derive_perm(master)` | Derives a 16-byte permutation from key |
|
|
184
|
+
| `STORY._expand_round_keys(master)` | Expands 13 round keys (12 rounds + output whitening) |
|
|
185
|
+
| `STORY._encrypt_block(block, master, sbox, round_keys)` | Encrypts a single 16-byte block |
|
|
186
|
+
| `STORY._make_counter_block(nonce, counter)` | Builds a CTR mode counter block |
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
## How STORY Works
|
|
191
|
+
|
|
192
|
+
### The story as a key
|
|
193
|
+
|
|
194
|
+
Your story string is passed through `SHAKE-256` to produce a 32-byte Input Keying Material (IKM). From that, two keys are derived using HMAC-SHA256 in an HKDF-like expansion:
|
|
195
|
+
|
|
196
|
+
```
|
|
197
|
+
story → SHAKE-256 → IKM (32 bytes)
|
|
198
|
+
│
|
|
199
|
+
┌─────────┴─────────┐
|
|
200
|
+
▼ ▼
|
|
201
|
+
enc_key (32B) mac_key (32B)
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
### The cipher structure
|
|
205
|
+
|
|
206
|
+
Each 16-byte block goes through 12 rounds of an SPN. Each round applies:
|
|
207
|
+
|
|
208
|
+
```
|
|
209
|
+
1. AddRoundKey — XOR state with round key
|
|
210
|
+
2. SubBytes — S-box substitution (key-derived, unique per story)
|
|
211
|
+
3. ShiftRows — Fixed byte rotation across columns (guaranteed diffusion)
|
|
212
|
+
4. Permute — Key-derived byte permutation (additional confusion)
|
|
213
|
+
5. MixColumns — AES-style GF(2⁸) mixing (diffusion)
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
After the 12th round, a final `AddRoundKey` (output whitening) is applied using a 13th round key. This ensures the last transformation is key-dependent.
|
|
217
|
+
|
|
218
|
+
### CTR mode
|
|
219
|
+
|
|
220
|
+
Blocks are encrypted in Counter (CTR) mode, turning the block cipher into a stream cipher:
|
|
221
|
+
|
|
222
|
+
```
|
|
223
|
+
keystream = Encrypt(nonce || counter)
|
|
224
|
+
ciphertext = plaintext XOR keystream
|
|
225
|
+
```
|
|
226
|
+
|
|
227
|
+
This means:
|
|
228
|
+
|
|
229
|
+
- Encryption and decryption are identical operations
|
|
230
|
+
- Plaintext length is preserved exactly (no padding)
|
|
231
|
+
- Each nonce must be unique — STORY generates a fresh 8-byte random nonce per `encrypt()` call
|
|
232
|
+
|
|
233
|
+
### Encrypt-then-MAC
|
|
234
|
+
|
|
235
|
+
After encryption, an HMAC-SHA256 tag is computed over `nonce || ciphertext` using `mac_key`. Decryption verifies this tag **before** processing any ciphertext. This provides authenticated encryption — tampered ciphertexts are rejected before any data is returned.
|
|
236
|
+
|
|
237
|
+
```
|
|
238
|
+
tag = HMAC-SHA256(mac_key, nonce || ciphertext)
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
---
|
|
242
|
+
|
|
243
|
+
## Design Properties
|
|
244
|
+
|
|
245
|
+
| Property | Value | Notes |
|
|
246
|
+
|----------|-------|-------|
|
|
247
|
+
| Block size | 128 bits (16 bytes) | Same as AES |
|
|
248
|
+
| Key size | 256 bits (32 bytes, derived) | Derived from story via SHAKE-256 |
|
|
249
|
+
| Rounds | 12 | SAC converges at round ~4; rounds 5–12 are security margin |
|
|
250
|
+
| Mode | CTR | Stream cipher mode, no padding required |
|
|
251
|
+
| Authentication | HMAC-SHA256 | Encrypt-then-MAC |
|
|
252
|
+
| Nonce size | 64 bits (8 bytes) | Random per encryption, 2⁶⁴ block capacity |
|
|
253
|
+
| S-box | Key-derived | Fisher-Yates shuffle seeded from master key |
|
|
254
|
+
| Diffusion | ShiftRows + key-derived permutation + MixColumns | Guaranteed cross-column diffusion |
|
|
255
|
+
|
|
256
|
+
---
|
|
257
|
+
|
|
258
|
+
## Choosing a Good Story
|
|
259
|
+
|
|
260
|
+
The security of STORY depends entirely on how difficult your story is to guess. A story is stronger when it is:
|
|
261
|
+
|
|
262
|
+
- **Long** — more characters means more entropy. Aim for at least one full sentence.
|
|
263
|
+
- **Personal and specific** — something only you would write, not a famous quote
|
|
264
|
+
- **Unique** — not the title of a book, movie, or song
|
|
265
|
+
- **Unpredictable** — includes your own phrasing, not generic phrases
|
|
266
|
+
|
|
267
|
+
```python
|
|
268
|
+
# ❌ Weak stories
|
|
269
|
+
mystory = "hello"
|
|
270
|
+
mystory = "password123"
|
|
271
|
+
mystory = "To be or not to be" # famous quote — guessable
|
|
272
|
+
|
|
273
|
+
# ✅ Strong stories
|
|
274
|
+
mystory = "The summer I turned 14, my grandmother taught me to make dumplings in her small Beijing apartment. No Matter what you say the experience was great and I will always miss her. Her name was Shu Fei Yan."
|
|
275
|
+
mystory = "Ju Wenjun's 2023 world championship match lasted 14 games and I watched every one from Singapore."
|
|
276
|
+
```
|
|
277
|
+
|
|
278
|
+
> **There is no password recovery.** If you forget your story, the ciphertext cannot be decrypted. Write it down somewhere safe if it matters. Or perhaps use an unknown book from where you are pasting the story, Maybe from your personal research project? or maybe about yourself?
|
|
279
|
+
|
|
280
|
+
---
|
|
281
|
+
|
|
282
|
+
## Project Background
|
|
283
|
+
|
|
284
|
+
STORY began as **Project 035** in 2023 — a personal exploration of cipher design. The name JuCrypt comes from the name of Ju Wenjun.
|
|
285
|
+
|
|
286
|
+
The cipher is dedicated to **Ju Wenjun** (居文君), Women's World Chess Champion, whose name is embedded throughout the codebase as a tribute to her excellence.
|
|
287
|
+
|
|
288
|
+
> *"JuCrypt was made with love, not to compete against existing ciphers."*
|
|
289
|
+
|
|
290
|
+
---
|
|
291
|
+
|
|
292
|
+
## Comparison with Standard Ciphers
|
|
293
|
+
|
|
294
|
+
| Feature | STORY | AES-GCM | ChaCha20-Poly1305 |
|
|
295
|
+
|---------|--------|---------|-------------------|
|
|
296
|
+
| Purpose | Education / hobby | Production | Production |
|
|
297
|
+
| Peer reviewed | ❌ No | ✅ Yes (NIST) | ✅ Yes |
|
|
298
|
+
| Key input | Natural language story | Raw bytes | Raw bytes |
|
|
299
|
+
| Block size | 128 bits | 128 bits | Stream |
|
|
300
|
+
| Authentication | HMAC-SHA256 | GCM (GHASH) | Poly1305 |
|
|
301
|
+
| Speed | Moderate (pure Python) | Very fast (C/hardware) | Very fast |
|
|
302
|
+
| Formal security proof | ❌ No | ✅ Yes | ✅ Yes |
|
|
303
|
+
| Recommended for secrets | ❌ No | ✅ Yes | ✅ Yes |
|
|
304
|
+
|
|
305
|
+
---
|
|
306
|
+
|
|
307
|
+
## Contributing
|
|
308
|
+
|
|
309
|
+
Contributions are welcome, especially:
|
|
310
|
+
|
|
311
|
+
- Empirical test results (NIST SP 800-22, differential cryptanalysis)
|
|
312
|
+
- Advanced test results
|
|
313
|
+
- Performance improvements (while keeping the code readable)
|
|
314
|
+
- Documentation improvements
|
|
315
|
+
- Bug reports
|
|
316
|
+
|
|
317
|
+
Please open an issue before submitting a large pull request. If you wish to submit some confidential results of story, please reach me out via mail rather than opening an issue for a smoother conversation.
|
|
318
|
+
|
|
319
|
+
---
|
|
320
|
+
|
|
321
|
+
## License
|
|
322
|
+
|
|
323
|
+
Apache 2.0 License — see [LICENSE](LICENSE) for details.
|
|
324
|
+
|
|
325
|
+
---
|
|
326
|
+
|
|
327
|
+
## Thanks to
|
|
328
|
+
|
|
329
|
+
- **Ju Wenjun** — Women's World Chess Champion, the inspiration for this project
|
|
330
|
+
- Shannon, C.E. (1949) — *Communication Theory of Secrecy Systems*, for the basic foundation of this project
|
|
331
|
+
- Daemen & Rijmen — *The Design of Rijndael* (AES), for SBox ideas and many more.
|
|
332
|
+
|
|
333
|
+
---
|