Hello deon;

deon wrote to N1uro <=-

By today's standards, isnt most BBS software insecure?

I may have an old copy of sbbsecho, I don't know. Someone I tried to set up
to feed was able to turn on echos from other nets which were not allowed in
my config. This I do not want. It may be sysop error too... just not enough time for me to debug it at the moment.

... .. A boiled egg is hard to beat.
--- MultiMail/Linux v0.52
# Origin: Carnage - risen from the dead now on SBBS (432:1/157)
* Origin: Ham Inter-network Echomail Gateway. (21:1/143.0)

On 01-02-22 10:07, N1uro wrote to deon <=-

Hello deon;

deon wrote to N1uro <=-

By today's standards, isnt most BBS software insecure?

I may have an old copy of sbbsecho, I don't know. Someone I tried to
set up to feed was able to turn on echos from other nets which were not allowed in my config. This I do not want. It may be sysop error too... just not enough time for me to debug it at the moment.

Definitely a sysop error. You need to make use of echolist and the echolist keys feature of Synchronet to limit echomail access to specific FTNs. I haven't gone down this road, I use Mystic for my FTN hub, which automatically limits echo access to nodes from the same networks by default.


... "Mount your horses, men!!" "We're not that lonely, sir!!"
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)