[Feature request] an update of =ss init #1

Closed
opened 2020-01-27 04:23:53 -05:00 by pax · 3 comments

for the command =ss init why need the hash from the user, it would be better if the bot got the hash itself from secure-sign or just used the message.author.id for authentication.

for the command =ss init why need the hash from the user, it would be better if the bot got the hash itself from secure-sign or just used the message.author.id for authentication.

changed the description

changed the description
Bsian commented 2020-01-27 05:12:42 -05:00 (Migrated from gitlab.libraryofcode.org)

=ss init is actually directly linked to the SecureSign CLI, also serves as a security barrier. Also automatically getting the hash won't be possible as they're on different systems

`=ss init` is actually directly linked to the SecureSign CLI, also serves as a security barrier. Also automatically getting the hash won't be possible as they're on different systems
Bsian commented 2020-01-27 05:12:45 -05:00 (Migrated from gitlab.libraryofcode.org)

closed

closed
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: engineering/cloudservices#1
There is no content yet.