12/20/2012 09:15 AM 2,293 ECHOMODS.RUL
01/01/2013 11:15 AM 6,125 EMERGCOM.RUL
12/14/2012 10:15 PM 4,146 GUITAR.RUL
03/26/2017 11:18 PM 1,191 LS_ARRL.RUL
12/28/2012 12:15 PM 1,995 SWL.RUL
12/16/2012 09:54 PM 528 TUB.RUL
@PID: GED+W32 1.1.5-b20161221
@TID: Mystic BBS 1.12 A24
Where it goes from here is entirely up to the users of the Echolist.
Let me know what you'd like to see and I'll come up with something.
I'll also have to read up on Mod Rul to see what it did before,
besides corrupting the database so often! lol :)
.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| (:) Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'
... You're not paranoid if they're really after you...
SEEN-BY: 57/0 103/705 116/102 123/180 130/505 512 153/250 154/10 203/0 [...]
ml { over here... this is also one reason why the MOD UPDs for theseareas
ml { have had a empty RUL line in them for the last decade+... with the old ml { system, they would have been flushed after some period of time of not ml { being updated by a MOD RUL...Mod
My current efforts are to allow .RUL files where needed. I haven't thought out the whole process yet. All I know is with the old Echobase 3.48 the
Rul submissions VERY often crashed EB and corrupted the Database beyond repair, so I dropped the little used Rule sub-system from EList v4entirely
at first.
* An ongoing debate between mark lewis and Ben Ritchey rages on ...
ml { the main thing i was pointing out is that those files need to be
ml { removed and should have been a long time ago...
I got that, and a mechanism for pruning the files will be implemented, eventually.
ml { have numerous concerns but i'm not sure when/if i'll have time to
ml { write them down for you... the main thing, though, is security
and
The Echolist belongs to FIDONet
and is being re-built from the ground up.
If constructive feedback is lacking or missing altogether then it'll
be what I perceive as best practice, period.
ml { what happens if someone drops off a file with an existing name
that ml { shouldn't be dropped off by them... in other words, someone pretending ml { to be authorized to drop off that particular file...
kinda rings of
If someone spoofs the address of a valid user, there's not much I can
do for now. I validate each .RUL submission to a valid user.
The Echolist belongs to FIDONet
On 03-30-17 23:12, Ben Ritchey <=-
spoke to Mark Lewis about Re: .RUL files <=-
The Echolist belongs to FIDONet and is being re-built from the ground
up. If constructive feedback is lacking or missing altogether then
it'll be what I perceive as best practice, period.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,049 |
Nodes: | 15 (0 / 15) |
Uptime: | 169:09:28 |
Calls: | 233,559 |
Calls today: | 5 |
Files: | 60,153 |
D/L today: |
73 files (90,681K bytes) |
Messages: | 292,022 |