2.2a - Fixed password checking, if the crypted password is 28 chars long and not 13. (by Oliver Lehmann) ---------------------------------------------------------------------- 2.2 - added away patches - fixed action-logging ---------------------------------------------------------------------- 2.1beta1 - rewrote the channel system in the hope of fixing the topic bug. - rewrote the logging system - fixed a dcc bounce issue - fixed a core in the new channel system ---------------------------------------------------------------------- 2.1rc1 - muh is now capable of bouncing dcc's (mirc-style resume is also supported) - added optional IPv6 support (./configure --enable-ipv6) - seperated the listening/outgoing connection addresses - muh listens on: listenhost = "127.0.0.1"; - muh connects to a server on: bind = "127.0.0.1"; if listenhost doesnt exist, the value of bind="" is used. - added timeouts for servers we establish a tcp connection to, but that never get any further - added an autojoin on startup channel option - muh will reply to ctcp TIME with a real physical time - added support for RPL_ISUPPORT (005 numeric) - servers that send us ERROR will no longer be disabled. - added internal channel topic/topicsetter tracking to muh - added internal channel tracking to muh - the additional +o/+v message when resyncing has been removed, and the client determines their own status from the /NAMES reply - added highly configurable logging for channels, see muhrc - numerous small fixes ---------------------------------------------------------------------- 2.05d 19/06/00 - fixed segfault on authorization - fixed pass-checking for pirch ---------------------------------------------------------------------- 2.05c 19/03/00 - changed configure & check-muh to work with older bashs - fixed segfault when leaving without channels - fixed segfault on connect-server-notice - added forwardmsg-option - added host-based access-control - added msg-filter (people-option) - added altnickname-option - password can be stored in crypted form in muhrc now (see muh -c) - small bugfixes ---------------------------------------------------------------------- 2.05b 08/03/00 - fixed signal-bug that crashed muh with check-muh (*blush*), weird that this wasn't an issue in earlier versions - fixed configure-script for some platforms - kill -HUP will rehash muh now - _everything_ in muhrc is now rehash-able (listenport, bind, etc; see docs) - config-parser will now attempt to recover on error ---------------------------------------------------------------------- 2.05a 03/03/00 - fixed compile-bug under bsd (unknown O_SYNC-flag) - minor corrections ---------------------------------------------------------------------- 2.05 23/02/00 - fixed compiling/linking. tested it under linux, freebsd, sunos5.4, hpux and irix - fixed message-reading - muh won't float in limbo anymore on server-error (k-line, kill, collide, stoned, ...) - 'nevergiveup' added (muh will never terminate) - 'norestricted' added (muh will jump on restricted connection) - fixed binding under freebsd (and other platforms) - fixed &channel-behaviour once again - removed all fixed buffers - added 'PRINT'-command and changed 'JUMP'-behaviour - rewrote cfg-file-parser - improved error-handling & reporting - added command-line params - added ascii-cows - made a muh(1)-manual - 'rejoin' added (muh will attempt to rejoin channels after reconnect) - fixed nickname-behaviour for ircii - lots of other enhancements, fixes and cleanups ---------------------------------------------------------------------- 2.04 27/02/99 - well err...there's been a bug in rejoining/leaving channels. i'm sure i have not made this cause it's been working earlier so this must have been done by aliens. honestly. ---------------------------------------------------------------------- 2.03 21/02/99 - the socket-eof-hoops-do-i-really-consume-100%-cpu-time-now? has now finally been fixed - i wonder why i haven't noticed this bug earlier: if some person did a "/msg NiCk hey!" but your nick was really "nick" (uncapitalized) then muh didn't notice the message was for it (same for ctcps etc) - wrote some doc and made the whole stuff using autoconf. i'm quite new to this autoconf-stuff so if i made a mistake please let me know! - the motd isn't requested every time a client connects to muh - some useful information is displayed instead - fixed some other tiny bugs i really don't remember ---------------------------------------------------------------------- 2.02 23/09/98 - oh no, why in the world have i released 2.01 without noticing *this* bug? there was a really stupid bug with the op-message and the /me that's performed when the client disconnects. ---------------------------------------------------------------------- 2.01 22/09/98 - fixed a stupid bug that made muh crash at startup (glibc didn't mind) - removed all the %as-scan-thingies so muh is *supposed* to work with ansi-c compilers again (infact i've tested it under freebsd and it worked superb) - added a anti-idle 'feature' - made the awaynotice configurable - made connect() work with freebsd (it never worked until now!) - PONG-replies by the server weren't filtered properly - fixed some minor bugs - okeiokei, muh now works with sick-identifying-clients like pirch - muh now sends an additional +o-message when reintroducing a channel where muh's opped (kvirc-author: scan the names reply more carefully!) ---------------------------------------------------------------------- 2.0 11/09/98 - it's stable! - it's backdoor-free! (err, it has always been backdoor-free, really! :) - it's configurable now! just create a ~/.muh/-dir and copy the muhrc there! - full CTCP-support (ping, version, clientinfo, ...) - when it receives a message while no client is connected it lets the messaging person know that nobody's there (there's a flood-protection of course, it means it sends this message only once to every hostname - same with the ctcp-messages btw) - muh supports commands from now on, see /muh help for details (you might have to type /quote muh help or /raw muh help depending on your irc-client) - most of the bugs i got reported (thanks guys!) were corrected (or is it all of the bugs? i dunno) - muh should work on all the major networks now (irc,dal,under) the main-problem was that other ircd-versions than the one used on irc-net don't support PRIVMSG's in nick!user@host-format - muh can be bound to a specific ip-address (in case the machine muh's running on has more than one ip-address) - you might still get the bad-password-error when connecting with irc-clients like pirch...bug the author of the irc-client, it's not my fault! the suggested order for authenticating password-protected irc-sessions is PASS-NICK-USER (RFC1459) - if some windoze-coders are too stupid to follow that suggestion then their users should suffer from that :) - muh checks if the connection between muh<->server and muh<->client is still alive...if not it either jumps server or drops the client - the greeting-message (blahblah Welcome to IRC nick!user@host) is corrected so some irc-clients shouldn't get confused any more (like thinking they're really 'nick' or they're really running from 'host') - muh won't crash no more when connecting with a rev-dns-entry-less :) machine - i think that's it for now, see for yourself what else changed ---------------------------------------------------------------------- $Id: ChangeLog,v 1.24 2006/04/16 12:23:10 sys-op Exp $