X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=Changes;h=12216135525d40b7d8dd8dd5044d5b5d7b039944;hb=996fed89967a1fd4d8665a10fd73b9612aeb1606;hp=fa47aee0dc1e919fa88c2fd56aa1e36783aae570;hpb=61a666ccf108505f0cec2e5c682fde019fc3a051;p=spider.git

diff --git a/Changes b/Changes
index fa47aee0..12216135 100644
--- a/Changes
+++ b/Changes
@@ -1,12 +1,19 @@
+04Jan23=======================================================================
+1. Fillout DXCIDR, attach checks in PC61 and logins. Login that fail will 
+   simply disconnect, like locked out callsigns
+2. Fix qrz.com URL in stock Internet.pm.
+3. Fix DXHash issues (baddx, badnode, badspotter etc)
+30Dec22=======================================================================
+1. Add more BadWords (regex) checks.
 01Dec22=======================================================================
 1. Re-add some debugging to see which incoming PC protcol sentences are
    being dumped because of any bad content (words or calls) if debugging
    option 'nologchan' is set.
-2. Any line entered by a user is checked for badwords *before* being sent to
-   the command processing system.
-3. All debugging for badwords has the word 'badword' in it. So that one can
-   do a 'grepdbg -2 badword' and one should see who said it and all of what
-   they said. 
+2. All debugging for badwords has the word 'badword' in it. So that one can
+   do a 'grepdbg -1 badword' and one should see who said it and all of what
+   they said. Watchdbg will also work with this.
+3. My latest recommended additions to the badword list includes:
+   RU STOP SPOT DISGRACE CRM CRIM CRUD SUBHUMAN FASCIST DEGENERATE CATTLE CNT
 23Nov22=======================================================================
 1. The BadWord system has been rewritten. This change is pretty radical and
    needs to be used with care as a word that is entered will be reduced to the