diff --git a/md/README.md b/md/README.md new file mode 100644 index 0000000..ad42556 --- /dev/null +++ b/md/README.md @@ -0,0 +1,17 @@ +dox +=== + +Intro +----- + +The purpose of dox is to create a git repository for the documentation +we have created from projex. The goals are: + +1. download each etherpad in the projex pad +2. org-ify each pad +3. write a pandoc script to convert each to html +4. write a pandoc script to convert this to markdown + +for now, the file structure should be: + +\`\`\` . ├── css ├── html ├── md ├── org └── scripts README.md \`\`\` diff --git a/md/emacs.md b/md/emacs.md new file mode 100644 index 0000000..e29cc86 --- /dev/null +++ b/md/emacs.md @@ -0,0 +1,186 @@ +essential keystrokes: (TAB to open bullets) <-- do this lol C-x 1 to +return buffer to 1 window C-g to cancel a command C-h a to search for +commands tiling window: C-x \[1..3\] C-k cut C-y paste show only +headlines: navigate to first heading and do C-c C-k + +emacs org mode +============== + +Overview +-------- + +So there are two basic things that are useful about org mode: + +1. bullets are collapsible which makes it really easy to organize shit + and move it around collapsible items rule! +2. TODO items have a lot of functionality + +so, my goal is actually to take projex~demo~.org and make it something +that is formatted in org mode, and the **reason** for that is that then +we can export it using pandoc with clean html (which we can add a +loittle styling etc) .. . once we have a format established, we can +loosely require people to add to pads in that format so that chhanges +can be git pushed and incorportated into the html. You can see an +example of what the raw html looks like here: + + +### Bullets + +- headings are organized with \* + - M-<enter> to add new heading + - M-<left> or M-<right> to promote / demote heading +- TAB to expand/collapse trees + +### TODOs + +TODOs are actually probably not that relevant for projex because it's +more for internal use ... maybe. + +1. DONE demo emacs org mode to data + +2. DONE enable line wrap as default + +3. TODO re-write projex in org mode style + + - projex~demo~.org is the test run of this. + + + + - C-c C-t to cycle through todo-done + - You can add more options by adding \#+TODO: TODO ONHOLD | DONE + to the top of the page (requires restart) + +### links + +- link structure: \[ \[link\]\[desc\] \] (but without the spaces) +- [file](test.org) C-c C-o to open at point this creates a + split buffer. C-x o to switch between split buffers, C-x 1 to return + the buffer to a single one. + +### code syntax highlighting and evaluation + +emacs provides support for lots of languages and you can start an +interpreter and run code with C-c C-c (evaluate buffer) + +You can also do code blocks and tangle / weave for literate programming. + +My friend always used indent region and it was impressingly fast + +### IRC + +how can i restart and save session? (keep buffers) + +there's M-x revert-buffer or you can turn auto-revert-mode on so it will +reload every time the file changes. I've never used the second... rarely +the first, I always just close :P so i don't need to save it? it +members? no, you would have to save it. I always just do C-x C-c (closes +all buffers) and save them all. I blieve if you try to revert-buffer it +will prompt you to save. Do i do this after restarting or before? C-c +C-s saves all buffers, C-c C-c exits. + +M-x package-install circe <enter> M-x circe <enter> Can i +set a socks proxy? I am not sure... I don't understand all that v. well. + +last year i read an article/list post how outdated emacs' networking is +and RMS agreed. i think the thread went viral .. + +could be! + + +I was just gonna paste this :P + +how do i get into config mode? + +do you mean the customize emacs thing? + +to set socks-noproxy or socks-server. the config file .. + +the config file is at \~/.emacs you can also change \~/.emacs.d/init.el + +Thanks, i changed my mind and prefer to keep my sanity! + +re: tor: we should use it for w3m tho, yah? + +sure, always. :) does emacs mind if we take aways some sycalls from it? + +random notes +------------ + +### useful things overview + +So there are two basic things that are useful about org mode: + +1. bullets are collapsible which makes it really easy to organize shit + and move it around collapsible items rule! +2. TODO items have a lot of functionality + +The goal is to take projex~demo~.org (another file in this directory) +and format it into org mode. The **reason** is that then we can export +it using pandoc with clean html (which we can add a loittle styling etc) +.. . once we have a format established, we can loosely require people to +add to pads in that format so that chhanges can be git pushed and +incorportated into the html. You can see an example of what the raw html +looks like here: + +(I think it's a good strategy to hit enter like this when we're done +typing :) ) + +### Switching between emacs 'buffers' (where different documents are open in the same emacs instance) + +- to open projex~demo~.org: C-x C-f and then start typing proj and + then TAB (for autocomplete) + +- use C-x <left> and use C-x <right> to switch + between buffers. + +### making bullets + +So, I guess my first question is about how I make the bullets? + +1. like this + + 1. this is a sub-level + + Ok I'll give that a shot + + So to "attach" the bullet to the text under it, do I just add + asterisks to the text? + + like this: + +2. Bullet + + This is the text under it! + + Damn that's east's easy :) + + yeah! and, you can do it with all kinds of list items, and it's also + especially useful when you have long passages of text that you can + just hide by pressing TAB. + + Perfect :) So, I might try to just "bullet" this conversation. So I + think what I did there makes sense in terms of how I organized that? + + YEAH! One more thing: + + to make new bullets you can do ALT-enter (ALT is known as M , + so M-<enter>) + +3. bullet1 + +4. bullet 3 + +5. bullet 2 + +6. bullet 4 + + and then, to change the order, you can use M-<up> and + M-<down> ... to promote you can use M-<left> and + M-<right> (but this gets more complicated when you have + sub-trees, so we'll worry about that layter beucause that's what I'm + having problems with re; my keybindings) + + Note for noobs: You have to have the cursor under the bullet tomove + your text, not the text itself. + + diff --git a/md/index.md b/md/index.md new file mode 100644 index 0000000..7d3fee3 --- /dev/null +++ b/md/index.md @@ -0,0 +1,234 @@ +Introduction +============ + +The purpose of this project is to protoype a process of collaborating +with strangers over the internet on mutual interests, with a trajectory +toward infosec/osint topics. Its current manifestion is a series of +'Anarchy Planet Tech Tuesdays' tutorials where we get together Tuesdays +8PM EST to go over a topic of choice. + +Goals include: + +- creating documentation of our proesses for internal use (and + possibly for sharing in the future if it doesn't suck) +- discovering and using (and possibly developing) FOSS tools, in + particular tools for collaboration +- creating a 'website' for keeping track of our notes that users can + edit, with some sort of version control (hopefully git) + +Feel free to generate your own tutorial topics, with the constraint that +the tutorials should be: + +1. short. something we can do together start to finish in 1-2 hours. +2. tangible. we should have something by the end that we didn't have + before, such as an email address with gpg enabled. +3. FOSS all day erry day + +bootsrapping +------------ + +This project has an implicit tagline: "Can we even get one tutorial off +the ground?" We all have felt the frustration of starting a project full +of enthusiasm and motivation to accomplish huge goals, only for the +initial excitement to wane as people get busy and drift on to other +tasks. So this project is about starting small. Can we even complete one +tutorial together? Can we break our grand plans into tiny projects that +we can execute without requiring massive amounts of people capable of +devoting massive amounts of time and energy? And if we can't, how can we +hope to accomplish larger and messier goals without repeating the cycle +of early enthusiasm and eventual burnout? + +tutorials +--------- + +Another motivation is to develop a process of creating documentation +through 'user testing'-- that is, understanding what someone needs to +know in order to accomplish a task, and then providing that information +and that information only. I find this more helpful than providing +someone the entire history of the internet and expecting them to develop +a deep understanding of every related concept and skill every time they +try to read a tutorial. Ultimately I hope this will result in building a +shareable corpus of knowledge, but even if this task fails we will at +least have the pieces we create which should be already useful in +themselves. + +Finally, this project is about building rapport with our collaborators +as we go through this process together. At the very least we will end up +with onboarding documentation that can help new people who come into the +process late, or who decide to go through their own process. And at best +we will also have data about whether or not a group of +loosely-affiliated strangers on the internet can collaborate together to +work toward their goals, leveraging existing infrastructure that exists +by keeping track of their process and developing strategies for sharing +that process. Can we? + +Tech Tuesday Topics +=================== + +- setting up IRC to run through Tor (hexchat, irssi, freenode w/ tor) + +- Inspircd, Atheme Services, setting up channels + +- Novatore The Bot (i.e., Limnoria, python) + +- using fishlim with hexchat / irssi: + +- setting up and using GPG: +- setting up ssh keys +- xmpp with OTR and OMEMO +- setting up host files to block advertisements + (beware effects + on fingerprintability) +- VPNS + +- host your own IRC +- self-hosting w/ Nginx +- make etherpad not require the *p* (i.e. nginx) +- audio streaming +- osint +- send and receive bitcoin (and/or other cryptocurrency? and setting + up group wallets?) + +- set up i2p + +- ipfs +- mesh +- bootloaders: how do they work? <3 +- zsh - Plugins: + - zsh.org - + + +tools +===== + +email resources + + +wiki + +fileshare resources syncthing +gobby (collaborative writing / code development) + - setup server: + + +git resources gitea gitosis + gobalist + gogs gitweb + +IRC atheme + + + briar + + +terminals if you love your console: apt search dwm tmux + +- post text and images - + +- bash scripts (for, {}, ..) + +editos emacs-orgmode vi + focuswriter + +forums (meh) session: together test which cms of +@LIST is eaiest to setup + +imgboard (chans not run by neonazis, maybe?) anokchan.org ;-) <3 + +privacy 'privacy' is a myth but that doesn't mean we should just give +all of the companies and the state all of our data. it actually matters +a lot (i.e. they are very much able to invade your life in powerful ways +by mining your data) <3 <3 + + + TAO / JTRIG + + + + +self-hosting sql + mail + +redis + +- easy backup: +- sharing files: + +- load balancing: + +tor tor is more than a anonymization client but has a wide ecosystem: + + + +'is tor safe' see vanguards: Possible quests: install the ooni app on +your smartphone to measure censorship: + +set up a cdn with two onion nodes via onionbalance publish a git +repository via globalist and let everyone in the group add a commit +create damn secret underground chat group with cwtch.im "Warning: Cwtch +is an experimental prototype. Please do not use it for anything where +security, privacy, or anonymity is critical." lol create an onion farm +with tor controllers like bine stem or carml run tor-ramdisk in a vm +secure communication find out why Perfect Forward Secrecy and metadata +protection are important have an end to end encrypted goup chat: + meet via voice/video chat: use +OMEMO alternatives: + Be +careful with your phones and tell your friends: + +read more on security ie. + + +cgAn + + + + + + + connect to freenode via tor: + + +fun + + +admin + +wanna start coding? + + +play around with tor: & + set up a cdn +with two onion nodes via onionbalance publish a git repository via +globalist and let everyone in the group add a commit create damn secret +underground chat group with cwtch.im create an onion farm with tor +controllers like bine stem or carml run tor-ramdisk in a vm secure +communication find out why Perfect Forward Secrecy and metadata +protection are important use riseup invite to get a new email account: + or any of + register an +account at create encrypted mailinglist: + try bitmask +VPN - lookout for the beta snap package use XMPP with +OTR/OMEMO for instant messaging + background: + - "the internet has +become a tool of the police state" + OTR encryption: + - for pidign.im install the package +pidgin-otr OMEMO encryption: + (not so widely +supported yet) have an end to end encrypted goup chat: + meet via voice/video chat: +alternatives: + Be +careful with your phones and tell your friends: + +read more on security ie. + + +Use globalist: + +Add to torrc: HidServAuth jyx4pglulzhhf3uj.onion KDaoFiimBt9GL6MKF7U2bw +as root: apt install python3-pip as user: cd globalist ; torsocks pip3 +install . diff --git a/md/irc-how-to.md b/md/irc-how-to.md index 486c90f..f753bc7 100644 --- a/md/irc-how-to.md +++ b/md/irc-how-to.md @@ -1,30 +1,5 @@ Anarchy Planet IRC how to ========================= - -**Table of Contents** - -- [Anarchy Planet IRC how to](#anarchy-planet-irc-how-to) - - [How to Connect](#how-to-connect) - - [web](#web) - - [using a client](#using-a-client) - - [using tor](#using-tor) - - [Basic Commands](#basic-commands) - - [Managing Nicknames (Nickserv)](#managing-nicknames-nickserv) - - [Managing Channels (ChanServ)](#managing-channels-chanserv) - - [Moderating Channels](#moderating-channels) - - [Ban Examples:](#ban-examples) - - [Advanced Commands for the uberl337 **\***](#advanced-commands-for-the-uberl337-) - - [Advanced NickServ commands](#advanced-nickserv-commands) - - [Advanced Chanserv commands](#advanced-chanserv-commands) - - [Access lists](#access-lists) - - [Access levels](#access-levels) - - [AOPs](#aops) - - [SOPs](#sops) - - [Viewing AOP and SOP lists](#viewing-aop-and-sop-lists) - - [AKICKs](#akicks) - - [Color codes](#color-codes) - - How to Connect -------------- @@ -35,8 +10,8 @@ How to Connect ### using a client -irc.anarchyplanet.org port 6667 irc.anarchyplanet.org port 6697 (SSL) -km3jy7nrj3e2wiju.onion port 6667 || 6697 +\`\`\` irc.anarchyplanet.org port 6667 irc.anarchyplanet.org port 6697 +(SSL) km3jy7nrj3e2wiju.onion port 6667 || 6697 \`\`\` ### using tor @@ -106,36 +81,37 @@ unlock all of a channel's modes, use Moderating Channels ------------------- -/kick nickname!userid@hostname removes user from channel, but does not +`/kick nickname!userid@hostname` removes user from channel, but does not ban them. They are able to join immediately. -/ban nickname!userid@hostname bans user from channel, but does not kick -them. They are prevented from speaking but can still see the channel. +`/ban nickname!userid@hostname` bans user from channel, but does not +kick them. They are prevented from speaking but can still see the +channel. -/kickban nickname!userid@hostname +`/kickban nickname!userid@hostname` -Use /whois, /whowas or /who to find the information necessary for a ban. -note: \* is a wildcard and can replace nickname, userid, parts of -nickname or userid, hostname or a segment of a hostname. +Use `/whois`, `/whowas` or `/who` to find the information necessary for +a ban. note: `*` is a wildcard and can replace nickname, userid, parts +of nickname or userid, hostname or a segment of a hostname. -/mode \#channel +b nickname!userid@hostname the same as /ban +`/mode #channel +b nickname!userid@hostname` the same as /ban ### Ban Examples: -joe!\*@* Will prevent anyone with the nick joe from joining. +`joe!*@*` Will prevent anyone with the nick joe from joining. -**myg0t**!\* Will prevent anyone whose nick contains myg0t from joining. +`*myg0t*!*` Will prevent anyone whose nick contains myg0t from joining. -mark!\*elc@\* Will prevent anyone with the nick mark and the userid elc +`mark!*elc@*` Will prevent anyone with the nick mark and the userid elc from joining. -\*!\*@c-123-24-76-213.ga.isp.net Will prevent anyone with the host +`*!*@c-123-24-76-213.ga.isp.net` Will prevent anyone with the host c-123-24-76-213.ga.isp.net from joining. -\*!\*@* Bans everyone. Don't do that. +`*!*@*` Bans everyone. Don't do that. -Advanced Commands for the uberl337 **\*** ------------------------------------------ +Advanced Commands for the uberl337 +---------------------------------- ### Advanced NickServ commands @@ -147,49 +123,46 @@ Advanced Commands for the uberl337 **\*** mode outside of a channel, use `/mode nickname #channel +/- attributes` - Some of the more important ones are: - `+q: User is owner of the current channel (prefix ~ or @)` - `+a: User is an admin (SOP) on the current channel (prefix & or @).` - `+o: User is an operator (AOP) on the current channel (prefix @).` - `+h: User is a half-op on the current channel (prefix %).` - `+v: User has voice on the current channel (prefix +).` + Some of the more important ones are: `+q` User is owner of the + current channel (prefix \~ or @) `+a` User is an admin (SOP) on the + current channel (prefix & or @). `+o` User is an operator (AOP) on + the current channel (prefix @). `+h` User is a half-op on the + current channel (prefix %). `+v` User has voice on the current + channel (prefix +). For a complete list of user modes visit ### Advanced Chanserv commands -1. Commands +`/msg chanserv set #channel secure [on|off]` Keeps everyone except aops, +sops, and the founder from becoming ops. - `/msg chanserv set #channel secure [on|off]` Keeps everyone except - aops, sops, and the founder from becoming ops. +`/msg chanserv set #channel keeptopic [on|off]` Maintains the topic even +if everyone leaves. - `/msg chanserv set #channel keeptopic [on|off]` Maintains the topic - even if everyone leaves. +`/msg chanserv set #channel enforce [on|off]` Restores op/halfop/voice +if a person with op/halfop/voice gets de-opped/halfopped/voiced. - `/msg chanserv set #channel enforce [on|off]` Restores - op/halfop/voice if a person with op/halfop/voice - gets de-opped/halfopped/voiced. +`/msg chanserv set #channel leaveops [on|off]` Whether or not to allow +the first person who join the channel to get ops. - `/msg chanserv set #channel leaveops [on|off]` Whether or not to - allow the first person who join the channel to get ops. +`/msg chanserv drop #channel [dropcode]` Un-registers the current +channel to you with ChanServ. - `/msg chanserv drop #channel [dropcode]` Un-registers the current - channel to you with ChanServ. +`/msg chanserv set #channel founder [nickname]` Sets the current +channel's founder. - `/msg chanserv set #channel founder [nickname]` Sets the current - channel's founder. +`/msg chanserv set #channel desc [description]` Changes the current +channel's description. - `/msg chanserv set #channel desc [description]` Changes the current - channel's description. +`/msg chanserv set #channel url [address]` Associates a URL with the +channel. - `/msg chanserv set #channel url [address]` Associates a URL with - the channel. +`/msg chanserv set #channel [email@address]` Associates an email address +with the channel. - `/msg chanserv set #channel [email@address]` Associates an email - address with the channel. - -2. Channel modes +1. Channel modes `/mode #channel +/-attribute [data]` @@ -200,10 +173,14 @@ Advanced Commands for the uberl337 **\*** `/msg chanserv access #channel add [nickname] [level]` Adds nickname to the channel's access list at the specified level. + `/msg chanserv access channel del [nickname]` Removes nickname from the -channel's access list. `/msg chanserv access #channel list` Displays the -channel's access list. `/msg chanserv access #channel count` Displays -how many entries are in the channel's access list. +channel's access list. + +`/msg chanserv access #channel list` Displays the channel's access list. + +`/msg chanserv access #channel count` Displays how many entries are in +the channel's access list. ### Access levels @@ -226,33 +203,47 @@ channel. ### SOPs -Can do everything AOPs can. Can give and take AOP privileges. Receive -memos sent to the channel's SOPs. Can add (but not remove) AKICKs. -\#\#Viewing and setting privileges +- Can do everything AOPs can. +- Can give and take AOP privileges. +- Receive memos sent to the channel's SOPs. +- Can add (but not remove) AKICKs. + +Viewing and setting privileges +------------------------------ ### Viewing AOP and SOP lists -/msg chanserv aop \#channel list /msg chanserv sop \#channel list adding -a AOP or SOP /msg chanserv \[AOP|SOP\] channel \[ADD|DEL|LIST|CLEAR\] -\[nick | entry-list\] +`/msg chanserv aop #channel list` + +`/msg chanserv sop #channel list` + +Add an AOP or SOP +`/msg chanserv [AOP|SOP] channel [ADD|DEL|LIST|CLEAR] [nick | entry-list]` ### AKICKs People on the AKICK list are automatically kicked and banned when they enter the channel. Bans made as a result of AKICK must be removed -manually. /msg chanserv akick \#channel add host \[reason\] Adds host to -\#channel's AKICK list \[for reason\]. /msg chanserv akick \#channel del -host Removes host from the AKICK list. /msg chanserv akick \#channel -list /msg chanserv akick \#channel view Displays the AKICK list. +manually. + +`/msg chanserv akick #channel add host [reason]` Adds host to +\#channel's AKICK list \[for reason\]. + +`/msg chanserv akick #channel del host` Removes host from the AKICK +list. + +`/msg chanserv akick #channel list` `/msg chanserv akick #channel view` +Displays the AKICK list. ### Color codes -it's possible to color your text in irc. in most clients you can use +It's possible to color your text in irc. in most clients you can use control c then foreground,background (background is optional). examples: red text ^c4^. black text on a blue background ^c1^,2. here's a full list of the color codes: -Number Name 00 white 01 black 02 blue (navy) 03 green 04 red 05 brown -(maroon) 06 purple 07 orange (olive) 08 yellow 09 light green (lime) 10 -teal (a green/blue cyan) 11 light cyan (cyan / aqua) 12 light blue -(royal) 13 pink (light purple / fuchsia) 14 grey 15 light grey (silver) +\`\`\` Number Name 00 white 01 black 02 blue (navy) 03 green 04 red 05 +brown (maroon) 06 purple 07 orange (olive) 08 yellow 09 light green +(lime) 10 teal (a green/blue cyan) 11 light cyan (cyan / aqua) 12 light +blue (royal) 13 pink (light purple / fuchsia) 14 grey 15 light grey +(silver) \`\`\` diff --git a/md/ircwalkthrough.md b/md/ircwalkthrough.md new file mode 100644 index 0000000..58f6d94 --- /dev/null +++ b/md/ircwalkthrough.md @@ -0,0 +1,211 @@ +Anarchy Planet IRC Walkthrough Tutorial +======================================= + +basic commands: + +Questions +--------- + +Q: will you leave the channel? I want to see what hpapens to ops, e.g., +can I take them A: One needs to leave and join again to take over an +empty channel. + +Q: How do i identify the bot automatically using SASL or certificates? +A: + +\^ f you get an error about “Insufficient parameters for CERT”, CertFP +is supported, and if you get an error about unknown command, it’s not +supported. \^ this is why I was trying to figure out how to enable +SASL... + +Inspircd inspircd user modes: +inspircd channel modes: + +to become an IRC pro, do these tasks! register a nick get a hostmask +group another nick Register a channel set MLOCK set entry msg make +private, secret, keyword-enabled Add people to access lists Fantasy Mode +atheme flags: + + +Limnora (i.e. Novatore) register with novatore create an alias add an +RSS + +Register a Channel <notnull>This IRC is two different things: +Inspircd and Atheme. Athme provides "services" which the best way to +think about them is that they are bots that take commands. +<notnull> chanserv, nickserv, memoserv, all are Atheme Services +<notnull> when you register a channel you are sending a command to +ChanServ to keep track of it <notnull> similiarly w/ your nick and +nickserv <notnull> channels have properties that are set with +flags <notnull> can you op me rfa? <notnull> do !op notnull +<rfa> !op notnull /\* ChanServ gives channel operator status to +notnull <notnull> the ! is called 'fantasy mode' <notnull> +it is an alias for /msg chanserv <notnull> you can set it to be +whatever you want, but yes ! is atheme default for chanserv +<notnull> !info -ChanServ- Information on \#poetry: -ChanServ- +Founder : rfa -ChanServ- Successor : (none) -ChanServ- Registered : Jan +01 19:30:41 2019 -0800 (1h 33m 11s ago) -ChanServ- Mode lock : +nt-lk +-ChanServ- Flags : VERBOSE GUARD FANTASY -ChanServ- Prefix : ! (default) +-ChanServ- **\*** End of Info **\*** <notnull> so channels have +'flags' that give them properties <notnull> the channel info shows +the Mode lock: +nt-lk shows that this channel has the n and t flags +locked as being on, and the l and k flags locked as being off +<notnull> so I can never remember what these stupid flags are, but +I'll just start with k, which is 'keyword' <notnull> this channel +is 'locked' to have a -k flag, which means you can' tset a keyword (i.e. +password) for it because chanserv is guarding it /\* notnull sets +channel keyword to paswd /\* ChanServ removes channel keyword /\* +Channel \#poetry modes: +nst /\* Channel \#poetry created on Tue Jan 1 +22:29:50 2019 <rfa> yikes <notnull> so if you want to fix +that you have to remove it from the mlock <notnull> sooo the way +to do that is <notnull> !set mlock k -ChanServ- You may only alter ++OP modes. <rfa> !set mlock k <notnull> I got this result: +-ChanServ- You may only alter +OP modes. <rfa> "ChanServ:The MLOCK +for \#poetry has been removed." /\* notnull sets channel keyword to +passwd /\* Channel \#poetry modes: +knst passwd /\* Channel \#poetry +created on Tue Jan 1 22:29:50 2019 <rfa> only ops can do this +right? <notnull> so you'll have to go through all the flags, I cna +never remeber what they all are, but you can, e.g.,make channels +private, invite only, all kinds of stuff. <notnull> yes and there +are also different access levels <rfa> and there's no need to lock +a normal, open channel, right? <notnull> !access list -ChanServ- +Entry Nickname/Host Role -ChanServ- ----- ---------------------- ---- +-ChanServ- 1 rfa <Custom> -ChanServ- ----- ---------------------- +---- <notnull> so, access lists are actually just 'templates' of +flag groups <notnull> there are channel flags and user flags +<Fauvenoir> flags... set... mode.... what's the difference? +<notnull> good question ;) <notnull> !help flags -ChanServ- +**\*\*\*** ChanServ Help **\*\*\*** -ChanServ- Help for FLAGS: +-ChanServ- -ChanServ- The FLAGS command allows for the granting/removal +of channel -ChanServ- privileges on a more specific, non-generalized +level. It -ChanServ- supports nicknames, groups and hostmasks as +targets. -ChanServ- -ChanServ- When only the channel argument is given, +a listing of -ChanServ- permissions granted to users will be displayed. +-ChanServ- -ChanServ- Syntax: FLAGS <\#channel> -ChanServ- +-ChanServ- Otherwise, an access entry is modified. A modification may be +-ChanServ- specified by a template name (changes the access to the +-ChanServ- template) or a flags change (starts with + or -). See the +-ChanServ- TEMPLATE help entry for more information about templates. +-ChanServ- -ChanServ- If you are not a founder, you may only manipulate +flags you -ChanServ- have yourself, and may not edit users that have +flags you -ChanServ- don't have. For this purpose, +v grants the ability +to grant -ChanServ- +V, +h grants the ability to grant +H, +o grants the +ability -ChanServ- to grant +O, and +r grants the ability to grant +b. +-ChanServ- -ChanServ- -ChanServ- -ChanServ- If you do not have +f you +may still remove your own access -ChanServ- with -\*. -ChanServ- +-ChanServ- Syntax: FLAGS <\#channel> \[nickname|hostmask|group +template\] -ChanServ- Syntax: FLAGS <\#channel> +\[nickname|hostmask|group flag~changes~\] -ChanServ- -ChanServ- +Permissions: -ChanServ- +v - Enables use of the voice/devoice commands. +-ChanServ- +V - Enables automatic voice. -ChanServ- +h - Enables use of +the halfop/dehalfop commands. -ChanServ- +H - Enables automatic halfop. +-ChanServ- +o - Enables use of the op/deop commands. -ChanServ- +O - +Enables automatic op. -ChanServ- +a - Enables use of the +protect/deprotect commands. -ChanServ- +q - Enables use of the +owner/deowner commands. -ChanServ- +s - Enables use of the set command. +-ChanServ- +i - Enables use of the invite and getkey commands. +-ChanServ- +r - Enables use of the kick, kickban, ban and unban +commands. -ChanServ- +R - Enables use of the recover, sync and clear +commands. -ChanServ- +f - Enables modification of channel access lists. +-ChanServ- +t - Enables use of the topic and topicappend commands. +-ChanServ- +A - Enables viewing of channel access lists. -ChanServ- +F - +Grants full founder access. -ChanServ- +b - Enables automatic kickban. +-ChanServ- +e - Exempts from +b and enables unbanning self. -ChanServ- +-ChanServ- The special permission +\* adds all permissions except +b and ++F. -ChanServ- The special permission -\* removes all permissions +including +b and +F. -ChanServ- -ChanServ- Examples: -ChanServ- /msg +ChanServ FLAGS \#foo -ChanServ- /msg ChanServ FLAGS \#foo foo!\*@bar.com +VOP -ChanServ- /msg ChanServ FLAGS \#foo foo!\*@bar.com -V+oO -ChanServ- +/msg ChanServ FLAGS \#foo foo!\*@bar.com -\* -ChanServ- /msg ChanServ +FLAGS \#foo foo +oOtsi -ChanServ- /msg ChanServ FLAGS \#foo +TroubleUser!\*@*.troubleisp.net +b -ChanServ- /msg ChanServ FLAGS \#foo +!baz +\* -ChanServ- **\*\*\*** End of Help **\*\*\*** <rfa> oh do +i need to set auto op for me so if i log out i don't lose it? +<notnull> no you would always be op as founder of the channel /\* +rfa (rfa@nihilist.abyss) has left /\* rfa (rfa@nihilist.abyss) has +joined /\* ChanServ sets mode +q on \#poetry rfa /\* ChanServ gives +channel operator status to rfa <notnull> hehee <rfa> yikes +<notnull> !set mlock + will remove all of the mlock flags, but +only founders can do it. <notnull> !set mlock + -ChanServ- You may +only alter +OP modes. <rfa> !set mlock + <rfa> ChanServ:The +MLOCK for \#poetry has been removed. <notnull> there are some +other things like <notnull> !set topiclock on -ChanServ- You are +not authorized to perform this command. <notnull> that keeps the +topic even when you leave <rfa> !set topiclock on +-ChanServ/\#poetry- rfa enabled the TOPICLOCK flag <notnull> and +!set guard on/off controls whether chanserv hangs out <rfa> nice +<notnull> also, if you don't want ChanServ you can make a custom +bot! <rfa> oh yes <rfa> if cs leaves that's bad, right? +<notnull> if you do /bs assign milieu \#poetry <rfa> why +would i ever want no cs? <notnull> it will be milieu instead of +chanserv <notnull> just a cooler name :P <rfa> what's bs +stand for? <rfa> !set guard on <rfa> ah botserv +<notnull> so your whole hostmask is +hex3@anarchy-planete17.kfm.ujrisk.IP <notnull> hex = nick, hex3 = +ident, all that other shit = hostname <notnull> a vhost changes +the hostname to something custom. <notnull> to get a vhost, you +request it from me. <hex> Oh ok, I see, give me a moment to think +of my new hostname. <notnull> hehe I can just make something +temporary for you? <hex> Violence.solves.everything? +<notnull> LOL love it. <notnull> the bots 'recognize' you by +your hostmask: that's the whole thing (nick!ident@hostname) +<notnull> so now, when you come here, if you aren't 'logged in', +ChanServ won't recognize you. <notnull> next: group a nick. +<notnull> you just change your nick to whatever, and then you /ns +group <notnull> you might wanna group hex~afk~ for example +<abyss> next: access lists. <abyss> do this: <abyss> +!access add notnull aop -ChanServ- You are not authorized to perform +this operation. <hex> !access add notnull aop +-ChanServ/\#hexchannel- hex added notnull to the access list (with role: +aop). <abyss> sweet <hex> What is the aop? <abyss> so +now I will be auto-opped every time I enter this channel <abyss> +!help access -ChanServ- **\*\*\*** ChanServ Help **\*\*\*** -ChanServ- +Help for ACCESS: -ChanServ- -ChanServ- The following subcommands are +available: -ChanServ- ADD Add an access list entry. -ChanServ- DEL +Delete an access list entry. -ChanServ- INFO Display information on an +access list entry. -ChanServ- LIST List channel access entries. +-ChanServ- SET Update an access list entry. -ChanServ- -ChanServ- For +more information, use /msg ChanServ HELP ACCESS command. -ChanServ- +**\*\*\*** End of Help **\*\*\*** <abyss> "AOP" in this context is +a template of permissions. <abyss> !access list -ChanServ- Entry +Nickname/Host Role -ChanServ- ----- ---------------------- ---- +-ChanServ- 1 hex <Custom> -ChanServ- 2 notnull AOP -ChanServ- +----- ---------------------- ---- -ChanServ- End of \#hexchannel ACCESS +listing. <abyss> there I am, AOP-tastic! <abyss> you can +remove it too using !access del notnull <abyss> !access del +notnull -ChanServ- notnull was removed from the AOP role in +\#hexchannel. <abyss> so you can get veeerrry precise about what +kind of access you give others. I don't use it that much, the server is +just too small. auto-op is one of the main ones that's important. +<hex> I assume you'd do that by adding and removing them from +various lists? <abyss> yes but ... you can actually put individual +flags on people. access lists are just templates. <abyss> so for +example you can !flags notnull +F <abyss> ;) <hex> !flags +notnull +F -ChanServ/\#hexchannel- hex set flags +Ff on notnull +<abyss> MWAHAHAHA <abyss> !info <abyss> - Founder : +hex, notnull <hex> What does that do? <abyss> hehe +<abyss> it gives me Founder access which is basiclally the highest +level <abyss> !access add plast aop -ChanServ/\#hexchannel- abyss +(notnull) added plast to the access list (with role: aop). /\* ChanServ +gives channel operator status to plast <abyss> see, now I can do +shit like that <abyss> oh yes, novatore <abyss> novatore is +a python-based IRC bot, but the best way to think about it is that it's +v. similar to the way services work. <abyss> so she takes +commands, her fantasy prefix is @ <abyss> but <abyss> you +have to register with her, just like you register with nickserv +<abyss> it doesn't have to be the same nick or anything +<hex> Is it helpful to use the same nick? <abyss> kind of... +but only slightly <abyss> nov recognizes you through your hostname +<abyss> whereas the Services bots authenticate your nick as well +<abyss> @help register <novatore> (register <name> +<password>) -- Registers <name> with the given password +<password> and the current hostmask of the person registering. You +shouldn't register twice; if you're not recognized as a user but you've +already registered, use the hostmask add command to add another hostmask +to your already-registered user, or use the identify command to identify +just for a session. This command (and all other (1 more message) +<abyss> @list <novatore> Admin, Alias, Anonymous, +AttackProtector, AutoMode, Channel, Conditional, Config, Games, Google, +Later, LinkRelay, MessageParser, Misc, Network, NickAuth, Note, Owner, +PluginDownloader, Quote, RSS, Reply, SedRegex, Seen, User, Utilities, +and Web <abyss> those are all of novatore's modules. diff --git a/md/kpcli.md b/md/kpcli.md new file mode 100644 index 0000000..a26d394 --- /dev/null +++ b/md/kpcli.md @@ -0,0 +1,3 @@ +useful commands + +show /eMail/gpg -f diff --git a/md/serverl337.md b/md/serverl337.md new file mode 100644 index 0000000..031ef9d --- /dev/null +++ b/md/serverl337.md @@ -0,0 +1,8 @@ +serverl337 +========== + +1. generate gpg key (gpg pad) gpg --gen-key +2. kpcli generate key + 1. bck/gpg + +3. diff --git a/update b/update new file mode 100755 index 0000000..ccf8a84 --- /dev/null +++ b/update @@ -0,0 +1,7 @@ +#!/bin/bash +cd $(dirname $0)/org +for org in *.org ; do + md=$(echo "$org"|sed -E "s/\.org$/.md/") + pandoc $org -o ../md/$md +done +cd ..