|
This is quickly devolving into basically us having to trust your word,the
Patrick. You're saying that you know something that we don't that makes
System i vulnerable.
sort ofFrom: Patrick Botz
The word "documented" is what makes the statement meaningless.
I know for a fact that the statement "has never been a case of any
statement....buffer overrun, virus, or indeed anything else on a native i5/Os
system..." (not the lack of the word "documented" in this
theIt is this statement that I know for a fact is not true.
Thanks.
This is quickly devolving into basically us having to trust your word,
Patrick. You're saying that you know something that we don't that makes
System i vulnerable.TCP/IP
I personally think that's bunk.
So let's try one last time, shall we? Is there currently an existing
vulnerability in V5R4M5 of i5/OS wherein an external agent can via
gain access to data or execute a program to which they are notauthorized?
prove
If the answer is no, then i5/OS is more secure than Windows, and this is
just a semantic digression. If the answer is yes, then I demand you
it, because it is a vulnerability in my system.fixed?
If the answer is "there was one, but we fixed it" then when was it
an
If the answer is no, is there a vulnerability other than TCP/IP by which
external agent can gain access to data or programs to which they are notthe
authorized?
Again, if the answer is no, then I don't know what we're discussing. If
it's yes, then what is the route? I don't need to know specifics, just
communication point. SNA? TELNET? Remember, it has to be external,vulnerable
meaning it can't involve physical access to the System i. If it's
command-line access, then that's a completely different animal.
Really, Patrick, your argument boils down to, "The System i is
and I know it." Whereas my argument is that Windows is vulnerable, andthe
whole world knows it.list
Joe
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.