Re: How Secure is Windows, Really?

If you're worried thast someone with a valid user profile and password will

do this sort of thing, then you better turn off ODBC immediately.

besides odbc, even from a cmd line with runsqlstm

Brian>Better yet, how about you create and distribute a freeware utility like....

It doesn't take freeware to create a backdoor.
I've seen them in commercial software. Doesn't have to even be malicious
in it's orginal intent. It's how the executing user uses it....
jim

To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, January 03, 2007 12:17 PM
Subject: RE: How Secure is Windows, Really?

Uh... you need a user profile and password to do that.  That's why it's a
bad idea to have user profiles and passwords in the wild, and also a bad
idea to allow SQL access to your machine.

If you're worried thast someone with a valid user profile and password will

do this sort of thing, then you better turn off ODBC immediately.

The big difference between iSeries attacks and Windows attacks is that a
number of the exploits we're talking about on Windows can bypass Windows

security. Just like the Rutkowska kernel code injection technique, they can

install software beyond the privileges of the user.

All these theoretical attacks on the iSeries require a valid user profile
and password, as well as the authority to the objects.

Joe

From: Walden H. Leverich

Really?... How about selecting all the tables from systables, then for
each table select all the numeric fields w/decimal positions and then
for each of them execute a sql statement that updates their values to
the effect of (set fld1 = fld1 * 0.01)... Easy to implement w/out any
knowledge of the underlying applications and subtle enough that it
probably wouldn't be noticed until lots of damage had occurred.