quality of life improvemnts

This commit is contained in:
cupcakearmy 2021-12-30 22:36:28 +01:00
parent c8b2539414
commit 2def365cae
No known key found for this signature in database
GPG Key ID: 3235314B4D31232F
5 changed files with 28 additions and 6 deletions

View File

@ -5,6 +5,17 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [1.3.1] - 2021-12-30
### Added
- Short explanation in the home page.
### Changed
- Explanation in about & readme.
- Shorten server ids from 512 to 256bit.
## [1.3.0] - 2021-12-22 ## [1.3.0] - 2021-12-22
### Added ### Added

View File

@ -30,7 +30,12 @@ Check out the demo and see for yourself https://cryptgeon.nicco.io.
## How does it work? ## How does it work?
each note has a 512bit generated <i>id</i> that is used to retrieve the note. data is stored in memory and never persisted to disk. each note has a generated <code>id (256bit)</code> and <code>key 256(bit)</code>. The
<code>id</code>
is used to save & retrieve the note. the note is then encrypted with aes in gcm mode on the
client side with the <code>key</code> and then sent to the server. data is stored in memory and
never persisted to disk. the server never sees the encryption key and cannot decrypt the contents
of the notes even if it tried to.
## Screenshot ## Screenshot

View File

@ -97,6 +97,10 @@
<br /> <br />
<Button on:click={reset}>new note</Button> <Button on:click={reset}>new note</Button>
{:else} {:else}
<p>
Easily send <i>fully encrypted</i>, secure notes or files with one click. Just create a note and
share the link.
</p>
<form on:submit|preventDefault={submit}> <form on:submit|preventDefault={submit}>
<fieldset disabled={loading}> <fieldset disabled={loading}>
{#if file} {#if file}

View File

@ -22,10 +22,12 @@
<AboutParagraph title="how does it work?"> <AboutParagraph title="how does it work?">
<span> <span>
each note has a 512bit generated <i>id</i> that is used to retrieve the note. the note is then each note has a generated <code>id (256bit)</code> and <code>key 256(bit)</code>. The
encrypted with aes in gcm mode on the client side and then sent to the server. data is stored in <code>id</code>
memory and never persisted to disk. the server never sees the encryption key and cannot decrypt is used to save & retrieve the note. the note is then encrypted with aes in gcm mode on the client
the contents of the notes even if it tried to. side with the <code>key</code> and then sent to the server. data is stored in memory and never
persisted to disk. the server never sees the encryption key and cannot decrypt the contents of
the notes even if it tried to.
</span> </span>
</AboutParagraph> </AboutParagraph>

View File

@ -20,7 +20,7 @@ pub struct NotePublic {
} }
pub fn generate_id() -> String { pub fn generate_id() -> String {
let mut id: [u8; 64] = [0; 64]; let mut id: [u8; 32] = [0; 32];
let sr = ring::rand::SystemRandom::new(); let sr = ring::rand::SystemRandom::new();
let _ = sr.fill(&mut id); let _ = sr.fill(&mut id);
return bs62::encode_data(&id); return bs62::encode_data(&id);