Re: VB connect to IBM i triggers Norton

[Thomas Garvey <tgarvey@xxxxxxxxxx>]

Thanks


Best Regards,

Thomas Garvey


On 3/10/2015 10:37 AM, Charles Wilt wrote:
> No, signing refers to using an certificate to sign the executable as a way
> to verify that it is unmodified and created by the company you think it is.
>
> See the section on SignTool.exe
> http://visualstudiomagazine.com/Articles/2013/05/01/Creating-Secure-Applications.aspx?Page=2
>
> Note: IBM signs the objects in the IBM i OS.
>
>
> On Tue, Mar 10, 2015 at 11:25 AM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:
>
> > But isn't it commonplace for Visual Basic applications to need to talk to
> > the iSeries?  Isn't the first step doing an 'open'?
> >
> > If our intent  for this application is a widespread release, it sounds
> > like we have to alert users they have to configure Norton to allow the
> > program to execute.
> > As for 'signing', I'm not sure what you mean.  Do you mean register it
> > with Norton so Norton sends updates to everyone that this app is OK?
> >
> >
> > Best Regards,
> >
> > Thomas Garvey
> > /<http://www.unpath.com/>/
> >
> > //
> >
> >
> >
> >
> >
> > On 3/9/2015 11:53 AM, Krill, Coy wrote:
> >
> > > That's a heuristic hit, which means it's not signature based, it's based
> > > on what the application is doing. It's opening a network connection to
> > > another host, so that can be seen as "bad" because Norton has never seen
> > > your in-house application which is "bad" and if you don't digitally sign
> > > your in-house windows software, it probably doesn't like it because it's
> > > unsigned which is also "bad". You can make an exception for it in Norton so
> > > that it leaves it alone and/or sign your app if it's not signed and see how
> > > it goes. In the banking industry we get lots of unsigned apps and we just
> > > whitelist them in Symantec as we know what they are and where they came
> > > from.
> > >
> > > Coy Krill
> > > Core Processing Administrator/Analyst
> > > Washington Trust Bank
> > >
> > > -----Original Message-----
> > > From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> > > Thomas Garvey
> > > Sent: Monday, March 09, 2015 09:41
> > > To: Midrange Systems Technical Discussion
> > > Subject: VB connect to IBM i triggers Norton
> > > Importance: Low
> > >
> > > If there is a better forum for this memo, please advise.
> > >
> > > We have a Visual Basic developer testing a VB program which needs to
> > > connect to our IBM i.  Once connected, this VB program will simply call a
> > > stored procedure on our box, which retrieves a value indicating authority
> > > is passed, or not.
> > > The program causes Norton to flag the program with SONAR.Heuristic.120,
> > > and deletes the VB executable, and forces a PC restart.
> > >
> > > The developer has narrowed the problem down to a single line of code,
> > > which connects to the iSeries host.
> > >
> > > cnHost.open()
> > >
> > > Here's what the developer is telling me...
> > >
> > > /I have defined cnHost as a variable instantiated to Microsoft's' ODBC
> > > Connection class within ADO.Net. The other class available from Microsoft
> > > is the OLEDB class. Both are similar. I tried both. There is no other way
> > > to connect to the iSeries Host except by the OPEN - regardless of the
> > > ADO.Net class being used and regardless of the programming platform being
> > > used (VB.Net, C#.Net, ASP.Net etc.) and regardless of the database
> > > (SQLServer, Oracle, DB2, Access, etc.).
> > > There's just no getting around this.//
> > > /
> > >
> > >
> > > So, why is Norton stopping us?  Is there something else we need to do?
> > >
> > >
> > >
> > > Best Regards,
> > >
> > > Thomas Garvey
> > > Corporate Scientist
> > > Unbeaten Path International
> > > 630-462-3991
> > > /www.unpath.com <http://www.unpath.com/>/
> > >
> > > //
> > >
> > >
> > > <www.unpath.com>
> > >
> > > --
> > > 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 electronic mail message and any attachments may contain confidential
> > > or privileged information and is intended for use solely by the
> > > above-referenced recipient. Any review, copying, printing, disclosure,
> > > distribution, or other use by any other person or entity is strictly
> > > prohibited under applicable law. If you are not the named recipient, or
> > > believe you have received this message in error, please immediately notify
> > > the sender by replying to this message and delete the copy you received
> > >
> > > ---------------------------------------------------------------------
> > --
> > 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.