7eaee3a89c
created WHY2_CHAT_CODE_KEY_EXCHANGE macro
2025-02-01 13:21:48 +01:00
bf354372ff
created why2_chat_ecc_deserialize_public_key fn
2025-02-01 13:03:21 +01:00
7bb6e38a99
created why2_chat_ecc_serialize_public_key fn
2025-02-01 12:55:39 +01:00
aa037bce74
WHY2_UPDATE_FAILED identifier fix
2025-01-31 17:12:04 +01:00
86c804b6c0
changed __WHY2_ACCEPT_THREAD_PARAMS identifier to lowercase
...
i forgot it isn't macro
2025-01-31 17:10:30 +01:00
2e53e63345
changed codes to shorter forms
...
also rename PM codes to DM codes but I already staged it and i am too lazy to redo it
2025-01-31 17:04:53 +01:00
316bdcc778
created _WHY2_ACCEPT_THREAD_PARAMS struct
2025-01-31 16:52:25 +01:00
1928519757
created WHY2_CHAT_SERVER_TYPE enum
2025-01-31 16:32:20 +01:00
8c80d3b815
added plain why2_authority_communicate_thread fn
2025-01-31 16:29:06 +01:00
78fc77cd69
created WHY2_CHAT_AUTHORITY_DIR macro
2025-01-31 15:59:14 +01:00
ee1c784b84
removed WHY_SA macro
...
first of all, its stupid. second thing - sa? seriously?
2025-01-31 15:56:17 +01:00
0994558a39
created WHY2_CHAT_AUTHORITY_PORT macro
2025-01-31 15:53:42 +01:00
2768280e7f
declared why2_chat_init_authority
2025-01-31 15:52:00 +01:00
1f9df8363a
added why2_send_socket_code fn
2025-01-31 12:39:55 +01:00
61fdb17018
created WHY2_CHAT_COMMAND_PM macro
2025-01-30 22:49:38 +01:00
e34f92b0d8
renamed WHY2_CHAT_COMMAND_PM to WHY2_CHAT_COMMAND_DM
...
Codacy Scan / Codacy Security Scan (push) Successful in 14s
Build WHY2-chat / test-why2 (./out/why2-chat-client, ./configure.sh, ubuntu-latest, ./out/why2-chat-server) (push) Successful in 1m49s
Test Project / test-project (./configure.sh, gdb -ex "run" -ex "quit" --batch, ubuntu-latest, ./test) (push) Successful in 2m6s
Test WHY2-core / test-why2 (why2, ./configure.sh, gdb -ex "run" -ex "quit" --batch, ubuntu-latest, ./out/why2-core-test, valgrind --leak-check=full --show-leak-kinds=reachable --track-origins=yes -s) (push) Successful in 2m12s
Test WHY2-logger / test-why2 (why2-logger, ./configure.sh, gdb -ex "run" -ex "quit" --batch, ubuntu-latest, ./out/why2-logger-test, valgrind --leak-check=full --show-leak-kinds=reachable --track-origins=yes -s) (push) Successful in 2m24s
these will be direct messages - unencrypted communication between two users
2025-01-30 21:20:59 +01:00
ac88620d99
added key parameter to why2_chat_ecc_verify_signature declaration
2025-01-30 20:06:20 +01:00
b859c88dcc
declared why2_chat_ecc_verify_signature
2025-01-30 19:38:02 +01:00
7c2c8b9138
created WHY2_CHAT_BASE64_LENGTH_DELIMITER macro
2025-01-30 19:37:49 +01:00
5cc8c43b62
declared why2_chat_ecc_sign
...
used for signing message with ECC
2025-01-29 21:13:59 +01:00
b977d0dd40
removed unused key macro
...
and renamed the key file
2025-01-29 20:50:54 +01:00
b833b56aef
changed up crypto header for ECC update
...
ill replace rsa with ecc i guess. Why? i fucking hate myself
2025-01-29 16:33:57 +01:00
520f8bce34
created anon fns for core-flags changed vars
...
calling sets flag without changing flag_changed variable
2025-01-13 19:54:44 +01:00
59d6252fe3
declared why2_get_padding_changed fn
2025-01-13 19:45:19 +01:00
0fe3f47752
added why2_set_padding fn
...
sets padding without messing with flags
2025-01-12 13:12:50 +01:00
e34b8b962f
changed why2_seed_random's seed to UL
2025-01-12 11:07:11 +01:00
25782d1263
changed why2_random to boolean
2025-01-10 18:09:55 +01:00
25113dc0b3
declared seeded-rand fns in crypto
2025-01-10 17:54:27 +01:00
67d6dfd0e7
raised curl timeout to 10
2025-01-09 16:25:05 +01:00
0a7e9ecee7
created WHY2_USER_CONFIG_DIR macro
...
stupid gitea runner making me do shit
2025-01-09 16:15:55 +01:00
cf277b249f
created WHY2_RECOMMENDED_PADDING_RATE macro
...
basically padding every 3 chars
2024-11-21 21:04:52 +01:00
1027042edf
added core-crypto to why2 header
2024-11-21 21:03:52 +01:00
326f8f0768
created WHY2_PADDING_NONZERO_TRIES macro
...
when I try to generate random number, I need to prevent it from being zero, so I try this many times to be non-zero before I forcefully set it to 1
this should run few times but yk, theoretically the generated number can be the same for infinite time (or at least slow the performance :) )
2024-11-21 20:50:20 +01:00
7dcbd4fc80
created why2_list_reverse fn in llist
...
it reverses list you dipstick
2024-11-21 17:59:15 +01:00
90643d8247
created why2_list_remove_at in llist
...
removes element by index
2024-11-21 17:20:47 +01:00
c5394e63e5
created why2_recalloc fn in memory
...
deallocates and callocs
2024-11-21 16:52:06 +01:00
0e246be627
created why2_list_push_at fn in llist
...
pushes to specific position
2024-11-21 16:49:27 +01:00
08181e5f19
renamed decrypter's key_new to key
...
haha same shit
2024-11-20 21:45:45 +01:00
5cc04d94b7
renamed encrypter's key_new to key
...
haha stupid old me was lazy af
2024-11-20 21:40:48 +01:00
f95608f52a
moved key's random number generation to why2_random fn
2024-11-20 17:56:04 +01:00
5b06ea5dc1
changed padding flag to UL
2024-11-20 17:12:54 +01:00
f754e43e19
made sum_segment comments more explanatory
2024-11-20 17:10:39 +01:00
6e7cdde99d
changed why2_sum_segment datatype to ULL
...
just in case
2024-11-20 16:33:22 +01:00
10fe26cca1
using rolling-hash-like way to count why2_sum_segment
2024-11-20 16:32:13 +01:00
b50305f080
created mod & base primes macros
2024-11-20 16:27:48 +01:00
e0274ec6c1
incread segment_size to 32
2024-11-20 16:24:21 +01:00
c0e9381642
renamed why2_checksum_segment to why2_sum_segment
...
it isn't that safe to be considered a checksum and the name checksum can be misleading. i am going to use it for getting padding size
2024-11-20 16:19:59 +01:00
c71b5275b5
changed checksum prime/segment ratio
2024-11-19 22:54:38 +01:00
2f6ab00f93
defined WHY2_CHECKSUM_PRIME macro
2024-11-19 22:28:10 +01:00
fb2ac1a7bb
moved checksum stuff to core-crypto
...
also created the core-crypto
2024-11-19 21:57:29 +01:00
