File: ChangeLog

package info (click to toggle)
muh 2.05d-7
  • links: PTS
  • area: main
  • in suites: woody
  • size: 496 kB
  • ctags: 637
  • sloc: ansic: 2,826; sh: 164; makefile: 132; lex: 105; yacc: 96
file content (212 lines) | stat: -rw-r--r-- 6,174 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
----------------------------------------------------------------------

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.17 2000/06/19 17:07:20 zap Exp $