Bitmessage/PyBitmessage-2025-02-25
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

SHA256 #792

Merged
Atheros1 merged 2 commits from sha256 into master 2015-03-27 20:45:37 +01:00
Conversation 0 Commits 2 Files Changed 5 +37 -16
Atheros1 commented 2015-03-27 20:42:30 +01:00 (Migrated from github.com)
Copy Link

Support SHA256 signatures. They won't be used by default; I'll coordinate with the developers of other implementations to work to get SHA256 supported. Then after an upgrade period we can start using it.

Support SHA256 signatures. They won't be used by default; I'll coordinate with the developers of other implementations to work to get SHA256 supported. Then after an upgrade period we can start using it.
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-25#792
No description provided.
Delete Branch "sha256"

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?