BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
be8b9021
Unverified
Commit
be8b9021
authored
Jan 07, 2018
by
Mattia Rizzolo
Committed by
Mattia Rizzolo
Jan 08, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update irker documentation to mention an irker bug with key-protected channels.
Signed-off-by:
Mattia Rizzolo
<
mattia@debian.org
>
parent
59b11c3d
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
1 deletion
+5
-1
irker.md
doc/user/project/integrations/irker.md
+5
-1
No files found.
doc/user/project/integrations/irker.md
View file @
be8b9021
...
...
@@ -47,4 +47,8 @@ Irker accepts channel names of the form `chan` and `#chan`, both for the
case,
`Aorimn`
is treated as a nick and no more as a channel name.
Irker can also join password-protected channels. Users need to append
`?key=thesecretpassword`
to the chan name.
`?key=thesecretpassword`
to the chan name. When using this feature remember to
**not**
put the
`#`
sign in front of the channel name; failing to do so will
result on irker joining a channel literally named
`#chan?key=password`
henceforth
leaking the channel key through the
`/whois`
IRC command (depending on IRC server
configuration). This is due to a long standing irker bug.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment