No description provided.
Announce ns identify deprecation and removal #2
Merged
hexa
merged 2 commits from 2025年10月23日 13:31:28 +02:00
ns-identify into master
hexa
commented 2025年10月22日 14:05:54 +02:00
hexa
force-pushed ns-identify from 2025年10月22日 14:07:16 +02:00
Compare
1968eca27d
to 1b2fdbfcde
major
reviewed 2025年10月22日 18:57:40 +02:00
home.md
Outdated
@ -7,0 +10,4 @@
From 2026年02月01日 the only supported authentication methods will be: SASL PLAIN, SASL EXTERNAL, SASL SCRAM-SHA-256, CertFP.
The rough list of reasons are that it is outdated, insecure, user-unfriendly way to transmit your credentials.
major
commented 2025年10月22日 18:57:40 +02:00
The rough list of reasons are that it is an outdated, insecure, and user-unfriendly way to transmit your credentials.
The rough list of reasons are that it is an outdated, insecure, and user-unfriendly way to transmit your credentials.
hexa marked this conversation as resolved
major
reviewed 2025年10月22日 18:58:37 +02:00
home.md
Outdated
@ -7,0 +14,4 @@
- Logging in only happens once you are connected, which can lead to races with room permissions
- Time and time again people have posted their credentials onto public channels
- The credentials also tend to get stored in your client logs that way
major
commented 2025年10月22日 18:58:37 +02:00
- Credentials tend to get stored in your client logs
- Credentials tend to get stored in your client logs
hexa marked this conversation as resolved
major
reviewed 2025年10月22日 18:59:13 +02:00
home.md
Outdated
@ -7,0 +15,4 @@
- Logging in only happens once you are connected, which can lead to races with room permissions
- Time and time again people have posted their credentials onto public channels
- The credentials also tend to get stored in your client logs that way
- Clients have a dedicated place to store your credentails these days
major
commented 2025年10月22日 18:59:13 +02:00
Not a drawback, but more a solution by clients. Remove completely?
Not a drawback, but more a solution by clients. Remove completely?
hexa
commented 2025年10月22日 19:15:25 +02:00
Moving it out of the list and mentioning it separately, because I think it is important to tell the story.
Moving it out of the list and mentioning it separately, because I think it is important to tell the story.
hexa marked this conversation as resolved
major
reviewed 2025年10月22日 19:01:31 +02:00
home.md
Outdated
@ -4,6 +4,22 @@ hackint is a communication network for the [hacker](https://en.wikipedia.org/wik
## News
### 2025年10月23日 Friendship with /ns identify ended. Now SASL PLAIN is your new best friend.
major
commented 2025年10月22日 19:01:30 +02:00
Maybe find a better way of saying it?
/msg nickserv identify
Maybe find a better way of saying it?
`/msg nickserv identify`
hexa marked this conversation as resolved
major
reviewed 2025年10月22日 19:03:09 +02:00
major
left a comment
Some thoughts
Some thoughts
hexa
force-pushed ns-identify from 2025年10月22日 19:16:33 +02:00
Compare
1b2fdbfcde
to a005d95f4b
hexa
commented 2025年10月22日 19:16:38 +02:00
Thanks, applied!
Thanks, applied!
hexa
force-pushed ns-identify from 2025年10月22日 19:17:22 +02:00
Compare
a005d95f4b
to eb4345a450
hexa
merged commit eb4345a450 into master 2025年10月23日 13:31:28 +02:00
hexa
deleted branch ns-identify 2025年10月23日 13:31:29 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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
hackint/web-content!2
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ns-identify"
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?