<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.3">
</HEAD>
<BODY>
It's arguable that crackers are in their right mind Barry, giving Norton and McAfee something to do and sell.<BR>
You are very right in the sense that there is little honey in the pot to attract them to jnos installations.<BR>
<BR>
On Sat, 2007-04-07 at 11:00 +0200, Miroslav Skoric (YT7MPB) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Barry Siegfried wrote:</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> Sure it is possible for somebody to do that. But who in his right mind</FONT>
<FONT COLOR="#000000">> would actually waste his time doing that?</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">I don't know but I want to ensure that my mailbox is secured in that </FONT>
<FONT COLOR="#000000">manner and I want to be sure I am the only person supposed to access my </FONT>
<FONT COLOR="#000000">system's configuration files. In fact, I saw various types of </FONT>
<FONT COLOR="#000000">permissions granted to 'ftpusers' and wonder if I have put things in the </FONT>
<FONT COLOR="#000000">right place.</FONT>
</PRE>
</BLOCKQUOTE>
On a Microsoft platform, the opsys offers nothing toward security.<BR>
On unix and Mac platforms, the opsys offers features that are not utilized.<BR>
Security is strictly a jnos feature - what jnos offers is the only game in town.<BR>
<BR>
The good news is that the amateur community seems pretty safe to operate with.<BR>
The bad news is that the amateur community is not exclusive - non-hams have access if they care to.<BR>
If you have configured all file access for users in /public and below then directories above /public are not accessible and jnos replies "permission denied".<BR>
But the sysop has access to all files on the host - even outside jnos root directory.<BR>
So (like unix) the operating advise is to use sysop a minimum and the user a maximum.<BR>
And especially keep the sysop passwords private and changing.<BR>
Plus - since the "@" password is not encrypted is is well not to use the feature on the air.<BR>
<BR>
If your work results in a very secure jnos, you might consider sharing your approach?<BR>
Best of luck Misko.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Regards,</FONT>
<FONT COLOR="#000000">Misko YT7MPB</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>