secretin / secretin-app Goto Github PK

Hello, is it possible to add an option to edit folder name?

If you type a wrong username when sharing a secret, the error "User not found" appears, but then it doesn't go away if you close the modal, or type a correct username.

How to reproduce :

1. On a secret, go to "who has access" tab
2. Share with a non-existing user
3. Share with an existing user

Hello !

It would be cool to provide a docker image with everything pre-built so that you just to configure some environment variables and you are ready to go with a local version of the app.

It is also a sort of documentation on how to set up the project for a production environment.

Blank screen after compiling windows electron app, because bad urlencoding to acces local file

It would be useful to have some sort of suggestion when typing the username I want to share a secret with.

This suggestion would be based on users with whom I have already shared secrets. There would be no autocomplete when sharing a secret with a user for the first time.

In the login page, we can't use the two factor rescue codes.

In entreprise context, sharing password is more likely to happen by group of people than by typing all usernames, which ones may change over time.

To make the sharing usable, I suggest to include group management

Hello,

Is it possible to add an "space" between "from" and "folder name" in delete action from the secret option menu:

When a user shares a secret, it is no longer visible inside the secret list (any mode : all, shared, etc).
It appears again when clicking the "refresh" button, or refreshing the browser tab.

The lib already stores history for all secrets, so it's just a matter of UI to display that information.

As a user I should be able to see the previous state of any secret that I can view.

The login field often contains the same value, for instance the email of the user.
It would save some time for the user to pre-fill this field with a value customizable in the settings.

We can see list written over the list...

I'm facing the following issue :

...
[4/4] Building fresh packages...
error /usr/lib/secretin-app/node_modules/electron: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: /usr/lib/secretin-app/node_modules/electron
Output:
Downloading SHASUMS256.txt
[============================================>] 100.0% of 2.93 kB (2.93 kB/s)
/usr/lib/secretin-app/node_modules/electron/install.js:48
  throw err
  ^

Error: Generated checksum for "electron-v1.7.8-linux-x64.zip" did not match expected checksum.
    at ChecksumMismatchError.ErrorWithFilename (/usr/lib/secretin-app/node_modules/electron-download/node_modules/sumchecker/build.js:41:124)
    at new ChecksumMismatchError (/usr/lib/secretin-app/node_modules/electron-download/node_modules/sumchecker/build.js:56:133)
    at Hash.<anonymous> (/usr/lib/secretin-app/node_modules/electron-download/node_modules/sumchecker/build.js:203:22)
    at emitNone (events.js:105:13)
    at Hash.emit (events.js:207:7)
    at emitReadable_ (_stream_readable.js:516:10)
    at emitReadable (_stream_readable.js:510:7)
    at addChunk (_stream_readable.js:277:7)
    at readableAddChunk (_stream_readable.js:253:11)
    at Hash.Readable.push (_stream_readable.js:211:10)

I Googled and I found the following electron issue with a working solution.

• Electron issue #9595

My two cents

When a user is granted access to a secret from another user, the secret will not be visible in the list of the destination user before pressing the "refresh" button twice, or refreshing the browser tab.

I would like to be able to hide some secrets from the main list, especially when it's secrets that have been shared with me.
Currently when someone shares something with me, it stays in my secrets list forever.

First thanks, secretin looks really promising and helps us a lot.
This is a suggestion, will it be possible to add an expiration date to secrets.
So owner of the secret could be notify if a password needs to be updated.
The goal of this will be to help putting in place secret renewal.

I'm facing the following issue while building application

$ yarn run build-css && NODE_PATH=./src node_modules/.bin/react-scripts build
Rendering Complete, saving .css file...
Wrote CSS to /usr/lib/secretin-app/src/index.css
Creating an optimized production build...
Failed to compile.

./src/components/App.js
  Line 18:  'propTypes' is not defined  no-undef

Search for the keywords to learn more about each error.

error Command failed with exit code 1.

I found out that upgrading react-scripts to latest version solve the problem.

After react-script upgrade:

$ yarn run build-css && NODE_PATH=./src node_modules/.bin/react-scripts build
Rendering Complete, saving .css file...
Wrote CSS to /usr/lib/secretin-app/src/index.css
Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  214.84 KB  build/static/js/main.9161ccd0.js
  4.5 KB     build/static/css/main.3dc3bc02.css

The project was built assuming it is hosted at https://secret-in.me.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  yarn global add serve
  serve -s build

Find out more about deployment here:

  http://bit.ly/2vY88Kr

Done in 21.94s.

We can create user with master password being a single letter.

We should provide indicator and avoid weak master password

The user should be able to add an arbitrary number of fields on a secret.
The name and type of those fields should be customizable.

Proposed field types :

• text (equivalent to the current login and url fields)
• password (equivalent to the current password field)
• textarea (for longer text)

By default, a new secret should contain a login and a password

The lib allows to set the following parameters when generating a password:

General rules

• length (default : 20 characters)
• human-readable (default: false)
• avoid similar characters (default: false)

Content rules

• containing numbers (default: true)
• containing symbols (default: true)
• containing mixed case (default: true)
• strict mode = containing at least one of each the enabled content rules (default: false)

We should add the UI to be able to change these settings when generating a password.
The user should be able to customize the defaults in settings.
The configuration for each secret should be stored.

Sometimes you need some context information or comment with a secret.
Adding a textarea field in the add secret form will be useful

Hello, is it possible to add an option to able moving a "secret" to another folder?

It would be great if password strength could be choosen before generating it like in Lastpass or Keepass.
The secretin-lib used to generate the password seems to support au lot of options, so a simple modal windows could do the job easily.