|
|
e6c570c2c7
|
prepared trim_string for non-why2-allocated strings
|
2024-04-20 11:32:18 +02:00 |
|
|
|
65135ac961
|
created why2_allocated fn
checks for why2-mem allocation
|
2024-04-20 11:22:09 +02:00 |
|
|
|
19ccc45e0a
|
created pm code
|
2024-04-19 20:09:23 +02:00 |
|
|
|
07a4eecd4e
|
removed the stupid exit command sending
using codes instead
|
2024-04-19 20:03:20 +02:00 |
|
|
|
d451030ad0
|
handling sigint signal
i'm really trying alex, i am
wicked game
|
2024-04-19 16:32:44 +02:00 |
|
|
|
e023207261
|
added help command
|
2024-04-19 16:08:54 +02:00 |
|
|
|
1fc78a2a30
|
sending server exit_cmd with the initial welcome message
|
2024-04-17 18:04:45 +02:00 |
|
|
|
c98184f1f5
|
created exit_cmd getter & setter
|
2024-04-17 18:03:40 +02:00 |
|
|
|
b2c945fe6d
|
implemented the exit_cmd macro
|
2024-04-17 17:45:21 +02:00 |
|
|
|
b2ca56e927
|
created WHY2_CHAT_COMMAND_EXIT macro
also the prefix
|
2024-04-17 17:43:25 +02:00 |
|
|
|
99c76285a2
|
added ID to connection node
|
2024-04-17 17:25:55 +02:00 |
|
|
|
f1fd7c07ea
|
fixed linked list linkage problems
First of all, is linkage even a word? :D Second thing, I am so fucking stupid...
|
2024-04-17 17:22:44 +02:00 |
|
|
|
586df77ff4
|
revert "added configure script source todo"
reverts commit abd8645ab06374a345f1698c313e3c6bfc363ed7.
turns out it breaks workflows
|
2024-04-13 17:19:07 +02:00 |
|
|
|
22e03ca06e
|
fixed base bug in exp_mod fn
|
2024-04-13 14:20:52 +02:00 |
|
|
|
6227b8eb0a
|
changed WHY2_CHAT_RSA_EXPONENT base to 62
so now it isn't 65537 but H33
|
2024-04-13 14:20:26 +02:00 |
|
|
|
d9483f02ca
|
fixed rsa crypto input strings & output base
|
2024-04-13 13:45:40 +02:00 |
|
|
|
9cf062565a
|
created why2_chat_rsa_pri_decrypt
|
2024-04-13 13:40:26 +02:00 |
|
|
|
2a9df2a4b9
|
moved why2_chat_rsa_pub_encrypt body into exp_mod
so in next commit, which will be decryption, I won't kms
|
2024-04-13 13:38:14 +02:00 |
|
|
|
b74995bbab
|
changed WHY2_CHAT_RSA_EXPONENT datatype to string
|
2024-04-13 13:37:06 +02:00 |
|
|
|
6487ea8b85
|
defined why2_chat_rsa_pub_encrypt
pog
|
2024-04-13 13:30:52 +02:00 |
|
|
|
ee3f319dd7
|
implemented why2_chat_deallocate_keys in client
|
2024-04-13 13:17:03 +02:00 |
|
|
|
62d2f10e65
|
declared why2_chat_rsa_pub_encrypt
|
2024-04-13 13:15:26 +02:00 |
|
|
|
5bd948c8a0
|
switched fopen for why2_fopen in crypto
whoopsie
|
2024-04-13 13:09:54 +02:00 |
|
|
|
60b437d4e8
|
implemented why2 crypto getters
bit fucked the file
|
2024-04-13 13:08:44 +02:00 |
|
|
|
8f3af8c7d1
|
defined why2_get_chat* rsa stuff fns
|
2024-04-13 12:32:43 +02:00 |
|
|
|
bb8436badd
|
added body for why2_chat_deallocate_keys
|
2024-04-13 12:32:19 +02:00 |
|
|
|
2755472534
|
declared why2_get_chat* rsa stuff fns
|
2024-04-13 12:28:50 +02:00 |
|
|
|
2f4c73ce09
|
created why2_chat_deallocate_keys fn
|
2024-04-13 12:26:47 +02:00 |
|
|
|
ef1f9bbf38
|
renamed why2_chat_generate_keys to why2_chat_init_keys
I think the name is much more self-explanatory now
|
2024-04-13 12:24:19 +02:00 |
|
|
|
abd8645ab0
|
added configure script source todo
|
2024-04-13 12:19:32 +02:00 |
|
|
|
274a3e1772
|
revert "sending ssqc on every message loop end"
this reverts commit b14c8de7105a9f570a227ce7f8608103b205eca9
it seems that I created the check for some reason
|
2024-02-26 15:19:41 +01:00 |
|
|
|
850ab11272
|
using latest toml version in rust module
|
2024-02-25 20:54:17 +01:00 |
|
|
|
4d6b29e4c6
|
implemented max_message_length in message loop
|
2024-02-25 20:34:18 +01:00 |
|
|
|
13d4e2f480
|
created max_message_length in server cfg
|
2024-02-25 20:25:38 +01:00 |
|
|
|
b14c8de710
|
sending ssqc on every message loop end
|
2024-02-25 14:23:53 +01:00 |
|
|
|
22282623af
|
implemented trim_string in message loop
|
2024-02-25 13:16:12 +01:00 |
|
|
|
157d56ac57
|
not disconnecting user on null message
|
2024-02-25 13:15:54 +01:00 |
|
|
|
47fd5f01b6
|
created trim_string fn
|
2024-02-25 13:15:29 +01:00 |
|
|
|
a141065189
|
addded null check to why2_deallocate
|
2024-02-25 12:25:29 +01:00 |
|
|
|
0abd38e877
|
fixed byte format overflowing
yippee
|
2024-02-24 21:56:43 +01:00 |
|
|
|
9734749c3e
|
implemented WHY2_OUTPUT_BYTE in decrypter
i choose literally the worst approach but YEAH...
...it doesn't work...
...it overflows...
|
2024-02-24 21:05:09 +01:00 |
|
|
|
226f9b3759
|
preventing encrypted bytes from being zero
|
2024-02-24 19:51:51 +01:00 |
|
|
|
23f7019883
|
defined why2_byte_format_length
|
2024-02-24 16:57:23 +01:00 |
|
|
|
bf64d848c7
|
declared why2_byte_format_length fn
you pass in string created using byte format and it returns the length of it
|
2024-02-24 16:55:10 +01:00 |
|
|
|
89d721fa9d
|
implemented WHY2_OUTPUT_BYTE in encrypter output
|
2024-02-24 12:52:06 +01:00 |
|
|
|
773591d452
|
implemented WHY2_OUTPUT_TEXT in encrypter
|
2024-02-24 12:48:38 +01:00 |
|
|
|
782e964fa2
|
made decrypter variables snake_case
|
2024-02-24 11:56:05 +01:00 |
|
|
|
58327f3046
|
made encrypter variables snake_case
|
2024-02-24 11:55:56 +01:00 |
|
|
|
21900e27cb
|
made encrypt & decrypt fn parameters snake_case
|
2024-02-24 11:51:31 +01:00 |
|
|
|
06ae819a82
|
added the WHY2_OUTPUT_TEXT enum to every why2_input_flags usage
|
2024-02-23 20:36:27 +01:00 |
|
