sigit/sigit.io
7
2
Fork 0
Code Issues 32 Pull Requests 2 Actions Packages Projects 1 Releases 5 Wiki Activity

Enable UPLOAD button (deprecate SIGN and VERIFY) #53

New Issue
Closed
opened 2024-05-17 10:30:54 +00:00 by b · 2 comments
b commented 2024-05-17 10:30:54 +00:00
Owner
Copy Link
  • This should also be shown on the home screen (before logging in)
    • If a decrypted SIGit is uploaded, we should show the verify screen (without a user)
    • If an encrypted SIGit is uploaded, we should first prompt for a login, and route to the decrypt page
  • For logged in, if encrypted, route to the decrypt page
  • For logged in, if decrypted, go to verify screen
  • If uploaded file is not a SIGIT file, then we should reject

image

- [ ] This should also be shown on the home screen (before logging in) * If a decrypted SIGit is uploaded, we should show the verify screen (without a user) * If an encrypted SIGit is uploaded, we should first prompt for a login, and route to the decrypt page - [ ] For logged in, if encrypted, route to the decrypt page - [ ] For logged in, if decrypted, go to verify screen - [ ] If uploaded file is not a SIGIT file, then we should reject ![image](/attachments/7199aab3-be08-4d9a-8c1d-673ad8a27708)
image.png
4.9 KiB
b changed title from Add VERIFY button to home screen to Add UPLOAD button to home screen 2024-05-17 11:04:27 +00:00
b changed title from Add UPLOAD button to home screen to Enable UPLOAD button (deprecate SIGN and VERIFY) 2024-05-17 11:06:09 +00:00
s commented 2024-05-19 19:26:59 +00:00
Owner
Copy Link

Now that we have removed the direct download link of sigit file from DMs, how will users get encrypted sigit files for the upload?

Now that we have removed the direct download link of sigit file from DMs, how will users get encrypted sigit files for the upload?
b added this to the MVP project 2024-05-22 15:06:08 +00:00
b commented 2024-05-22 15:07:03 +00:00
Author
Owner
Copy Link

linked to: https://git.sigit.io/sig/it/issues/73

closing this one

linked to: https://git.sigit.io/sig/it/issues/73 closing this one
b closed this issue 2024-05-22 15:07:03 +00:00
b removed this from the MVP project 2024-05-22 15:08:01 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#53
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?