Skip to content

Instantly share code, notes, and snippets.

View ChrisTyrrel's full-sized avatar

Chris Tyrrel ChrisTyrrel

  • Ogden, UT
  • 19:47 (UTC -06:00)
View GitHub Profile

The new version of ZNC is based off of ZNC-1.7.1, the current ZNC release. The goal with the ZNC upgrade was to keep things as vanilla as possible. The most notable PanicBNC change was the removal of server and network changes along with only allowing ident changes to Premium users.

This version also contains numerous security fixes, improvements, and features. Too many to list here so they're here, check past version 1.4. Yeah, it's been that long. The largest change will be the verification of all SSL connections.

SSL

Previously IRC connections using non-valid SSL certificates (expired, self-signed, etc) were allowed, this will no longer happen with the new ZNC version. With the increase of free certificate authorities such as Let's Encrypt, there is no reason to not have a valid SSL certificate, or not being using SSL at all.

PanicBNC will accept new SSL IRC network requests with invalid certificates but will not pr

@ChrisTyrrel
ChrisTyrrel / changelog.md
Created November 20, 2017 19:34
EliteBNC 1.6.5 Changelog

Fixes

  • Fixed build with OpenSSL 1.1.
  • Fixed build on Cygwin.
  • Fixed a segfault after cloning a user. The bug was introduced in ZNC 1.6.0.
  • Fixed a segfault when deleting a user or network which is waiting for DNS during connection. The bug was introduced in ZNC 1.0.
  • Fixed a segfault which could be triggered using alias module.
  • Fixed an error in controlpanel module when setting the bindhost of another user.
  • Fixed route_replies to not cause client to disconnect by timeout.
  • Fixed compatibility with the Gitter IRC bridge.
  • Fixed a regression of 1.6.4 which caused a crash in modperl/modpython.

Keybase proof

I hereby claim:

  • I am ChrisTyrrel on github.
  • I am christyrrel (https://keybase.io/christyrrel) on keybase.
  • I have a public key whose fingerprint is 512F 090D 0D0D FF20 5C95 ACAC B3A3 D366 F31C 0FE1

To claim this, I am signing this object:

@ChrisTyrrel
ChrisTyrrel / gateways.md
Last active February 28, 2016 06:04
Freenode and gateway cloaks.

Freenode and gateway cloaks

Gateways on freenode work a tad bit different on freenode than they do on other networks. They're given a cloak describing the gateway they're using.

Cloak Examples

  • PanicBNC: gateway/shell/panicbnc/x-*
  • EliteBNC: gateway/shell/elitebnc/x-*
  • BNC4FREE: gateway/shell/bnc4free/x-*

Autovoicing/auto Modes

Flags on I-Line cloak

Suppose I wanted to voice any BNC4FREE users by setting the ChanServ V flag on the I-Line cloak. The process would be as follows: