Re: Be very careful from now on...

["Jim Franz" <franz400@xxxxxxxxxxxx>]

> the OS isn't really the issue with polling places.  It is the compilation
> software that is the problem.

if  i can compromise the OS and sniff/log the password then
i have the application. many are Access database, which
has it's own holes. Now this is no different than any other
wan except that most people would be uncomfortable if they
knew nobody was watching the store, and the lack of
redundancy and auditability makes is scary (to me).
jim
----- Original Message ----- 
From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, February 13, 2004 4:02 PM
Subject: Re: Be very careful from now on...


> the OS isn't really the issue with polling places.  It is the compilation
> software that is the problem.
>
> ----- Original Message ----- 
> From: "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx>
> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
> Sent: Friday, February 13, 2004 3:50 PM
> Subject: RE: Be very careful from now on...
>
>
> > So which OS for polling places - Linux variation?
> >
> > -----Original Message-----
> > From: Jim Franz [mailto:franz400@xxxxxxxxxxxx]
> > Sent: Friday, February 13, 2004 2:30 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: Be very careful from now on...
> >
> >
> > Several years ago, it was reported that hackers had been inside
> > MS development systems for up to 30 days prior to MS realizing it.
> > The only thing new is the public perception and whether they got new
code.
> >
> > A side note that most of the electronic voting machines use MS OS's
> > and please don't tell me that thousands of city/county governments
> > are going to have a "tight" security system, especially when polling
> > stations
> > can be anywhere.
> >
> > The iSeries question: Think about how to protect your iSeries
> > given the assumption the local lan or wan has or could be compromised.
> > Are local lan iSeries passwords in the clear? There are some out there
> > already running ssl on the local lan. What checks might you do
> > do to verify (beyond user/pwd) the authenticity of work?
> > jim
> >
> > ----- Original Message ----- 
> > From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>
> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> > Sent: Friday, February 13, 2004 3:00 PM
> > Subject: Re: Be very careful from now on...
> >
> >
> > > First, anyone that touts "security through obscurity" is naive and
> > shouldn't
> > > be listened to anyway.
> > >
> > > Second, if it takes a Windows source code leak to make you worry about
> > > security, you are already way behind the curve.
> > >
> > > In all honesty, a Windows source code leak should have no real affect
on
> > > your security concerns because you should have had everything locked
> down
> > > under the assumption that your OS has the ability to be hacked
(whether
> it
> > > is AS/400, Windows, Unix or Nintendo).
> > >
> > > ----- Original Message ----- 
> > > From: "Hans Boldt" <boldt@xxxxxxxxxx>
> > > To: <midrange-l@xxxxxxxxxxxx>
> > > Sent: Friday, February 13, 2004 2:33 PM
> > > Subject: Re: Be very careful from now on...
> > >
> > >
> > > > Adam Lang wrote:
> > > > > Be careful about what?
> > > > >
> > > >
> > > > Some people have been touting the advantages of "security through
> > > > obscurity". That argument can no longer be used in defense of MS's
> > > > closed source O/S. With source code available for direct inspection,
> > > > there is the very real concern that unscrupulous people now have a
new
> > > > technique for discovering security holes in MS software. Anyone who
> uses
> > > > an MS O/S (which includes practically all of us) now has more reason
> > > > than ever to be concerned.
> > > >
> > > > Cheers! Hans
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > 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.
> > >
> > >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > 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.
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > 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.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> 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.
>
>