Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33806
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23541
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12847
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4193
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13586
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16053
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22012
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   900
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4785
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2802
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13066
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4277
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   28533
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2020
DOS_INTERNET   0/196
duplikat   6000
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
Möte FIDONEWS_OLD1, 49742 texter
 lista första sista föregående nästa
Text 25928, 179 rader
Skriven 2006-02-25 10:46:00 av Michiel van der Vlist (2:280/5555)
  Kommentar till text 25840 av Dale Shipp (1:261/1466.0)
Ärende: Elist mergers
=====================
 >>   My choice and the choice of more than 400 other moderators
 >> who choose to enter information about their echos there

 MVDV>> We don't really know if they all made a free choice do we?

 >    They had multiple choices -- they could have sent their
 > listings to Peter, they could have sent their listings to Thom
 > (as most did), they could have sent their listings to others who
 > were offering the service, or they could have not bothered to
 > send a listing to anyone.

But only one of those choices - sending it to Thom - would have satisfied the
requirement that it must be listed in the Z1 e-list in order to be carried by
the Z1 backbone.

 MVDV>> After all you guys have been telling us for years that
 MVDV>> unlisted echos would be taken off the Z1 backbone. There is
 MVDV>> a disticnt possibility that many moderators only listed
 MVDV>> their echos because they felt they had no choice.

 >   While I will easily grant you that they felt that they had
 > to list their echos onto whatever Elist the distribution systems
 > recognized, that was not Thom's list until *AFTER*

While it may be that it wasn't always Thom's list that was "the recognoised
list" it is sure is now, and so the question of freedom of choice regarding the
moderators there are in that list now, surely applies.

 >>    Personally, I think that such a desire is overkill.

 MVDV>> I don't. If I have to wait a month to get to know who the
 MVDV>> moderator of an echo is, I may as well wait for the monthly
 MVDV>> rules.

 >   See above.  If you really want to know what is on the
 > database *now*, then send it a query to ask it.

Which in NOT possible with as multiple lists that are only synchronised once a
month.

 MVDV>>> NOW, not a month ago. An out of date list is totally
 MVDV>>> useless. 48 hour is the maximum I would consider acceptable.
 >
 >>   You are posturing for effect, and your stated expectation is
 >>   unreasonable.

 MVDV>> Then let me tell you that the one and only instance where I
 MVDV>> thought I migh have some use for the echolist, I was put on
 MVDV>> the wrong foot because the informatio was out of date
 MVDV>> without me being aware of it.

 >   If you are talking about the Elist that Thom maintains, then
 > you could have gotten the information which was correct as of
 > the day you wanted it.

Had I been aware of it, yes. You are missing the point however: the point being
that the list I was using was useless because the information was outdated by
up to a month.


 >> Do you insist that the telephone company send you an
 >>   updated phone book every week?

 MVDV>> No, but I do require that they offer an alternative to get
 MVDV>> up to date information. And they do, I can call the

 >    As does the Elist that Thom maintains.

The synchronised lists of Thom and Peter that the Z1 sysops wanted could not
have provided that service.

 MVDV>> directory information service. And since a decade or so I
 MVDV>> can consult the on-line telephone directory.

 >   As you could do with the Elist that Thom maintains.

But not with a set of zonal lists synchronised only once a month.

 MVDV>> Peter Witschi offered the service of requesting an up to date list.
 >
 >   As does Thom.

See above.

 MVDV>> The Z2 community could have appointed or elected a successor.

 >    As the policy you keep saying is in effect in zone 2 states
 > should have been done.

Your interpretation. Mine says different.

Whatever way, the Z2 community decides not to appoint a successor and that was
the end of the official Z2 echolist.

That does NOT mean that Thom's list gets promoted from Z1 e-list to global
list. It still remains the Z1 e-list.

 MVDV>> What is needed is that you can SEND encryoted mail. You can
 MVDV>> send encrypted mal to me. See above.

 >   For one who keeps insisting that you have to be shown direct
 > evidence before you will believe anything, you certainly seem
 > reluctant to provide any to support the positions that you take.

What more is there to prove? I have told you how you can send encrypted netmail
to me and you confirmed that that should work. What more do you want?

 MVDV>> Anyway, coming to think of it: to update the echolist in a secure way,
 MVDV>> it is  not needed to encrypt the entire message. All that is
 MVDV>> needed is to encrypt the password. As the password already
 MVDV>> is a meaningless string, it would merely mean that it would
 MVDV>> be replaced y another string just as meaningless with the
 MVDV>> difference that the "password" that is now in the masssage
 MVDV>> is no longer sufficient to get the update processed. It
 MVDV>> also requires the key, which is only known to the moderator
 MVDV>> and the echolist keeper. If a router does not object to a
 MVDV>> message containing a password of "XyZzy", why would he
 MVDV>> object if it was replaced by "A4fJq5"?

 >   So you would have the Elist Keeper maintain a separate key
 > for every moderator who wants to send him a listing?  Rather
 > clumsy, and an extra burden.

Just one extra item on the dozen or so that the e-list keeper maintains for
every moderator. I see no problem if the e-list keeper sees no problem.

 MVDV>> My point is that there are many solutions for the cost problem, But
 MVDV>> you do  not want to hear it, you find excuses for rejection. All

 >    I am not looking for excuses.  I gave you the reasons that
 > existed back then.

Which I think were excuse. There were alternatives and I gave you some which
would not have involved any extra cost. But you reject all except the one that
involves a Z1 e-list keeper.

 MVDV>> you want to hear about is a solution where the list is NOT
 MVDV>> in the hands of a Z2 e-list keeper.

 >   I had no objection to there being an Elist keeper in zone 2.

Yeah, as long as he/she was not the only one and Z1 had their own...

 >>>  Never mind, telling me how you would encrypt it in a manner that
 >>> would allow me to decrypt it.

 MVDV>>> There are programmes for that. Not more difficuolt to set
 MVDV>>> up than the stuff needed to maintain an e-list.

 >   So you are attempting to tell me that setting up a secure
 > encryption and key distribution system is not difficult?  Trust me,

I never trust people who say "trust me".

 >>    So tell us all how you would set it up.  Don't duck the question.

 MVDV>> I am not going to write a tutorial on PGP. That would be

 >    Don't need a tutorial on PGP.  Send me your PGP key and
 > I'll try to see if my uplink will accept an encrypted netmail
 > for you. You can use netmail or you can use the email address below.

You should have my key by now.

 MVDV>> reinventing the wheel. The information is freely available
 MVDV>> at various places. PGP is freeware. I can make it
 MVDV>> requestable from my system too if you want.

 >   No need.  I've had it on my home computers for years, and
 > known about and understood the algorithms it uses for decades.

So your were just kicking up dust and trying  to get me to do some needless
work when you challenged me to explain how a message should be encrypted. Good
to know you employ such tactics.

Cheers, Michiel

--- Buy Danish
 * Origin: http://www.vlist.org (2:280/5555)