Educause Security Discussion mailing list archives

Re: FW: Michael - Patent Infringement Notice


From: Sam Stelfox <SStelfox () VTC VSC EDU>
Date: Thu, 8 Dec 2011 11:06:31 -0500

I know this can be a rough bit to swallow but this discussions seems to crop up every couple of years and I'd highly recommend everyone to find those threads before we start a new one. It can definitely be less than ideal to leave the lists open, but there are many people that are subscribed to this list legitimately from non-edu addresses.

Personally, I think leaving it open so people from other industries can see our discussions is a huge benefit. The people on this list are intelligent, and thoughtful with their responses. These responses are indexed publicly and people with similar problems can see the points and counterpoints with each one.

If a vendor violates the sanctity of that discussion, it's not because it's encouraged. More likely than not it was a thoughtless act by a vendor that chose not to read the rules, or if they have, chose not to abide by them. This is a disastrous decision on their part as it will cause them to lose more business than they gain as any respect they may have will be broken.

There are also legitimate uses for vendor's being able to see these lists without harassing the members. By understanding what the current concerns and directions different organizations are heading in they can choose to adjust their products and provide better features for us all. This last point is small, and many may argue with it, but I personally consider it valid none-the-less.

--
Regards,
Sam Stelfox
Network Administrator
Vermont Technical College

On 12/08/2011 10:54 AM, Chuck Dunn wrote:
I think participation in the list should be limited to .edu addresses
and that access to the archives be limited to those with Educause login
credentials.   We can protect future discussions even if we can't
expunge the past archives from the public space.    In my view, anyone
who posts security related or DMCA complaint information to a public
forum should be thinking long and hard about who is reading the posts.

Chuck

Charles F. Dunn
Information Security Officer
University at Buffalo
716-645-3582


On 12/8/11 10:29 AM, Ken Connelly wrote:
There are guidelines, and EDUCAUSE generally does a good job of helping
to enforce them.  That said, the list is public and archived/available
on the web.  Even if vendors and trolls aren't list members, they can
still see what's been said.  Even if that's removed or restricted to
EDUCAUSE/list members only, it's been available and you have to presume
that there are copies other than the one that EDUCAUSE maintains.

I think that Dennis has made a huge mistake here, but I find that
vendors tend to think differently than I do.

- ken

Hanson, Mike wrote:
Valerie and Rodney,

Why are non .edu people allowed to post on this forum and threaten
legal action?

What is the value of this forum if it is not the free exchange of
information between .edu's?

Members are asking for and seeking advice on particular products and
implementations. Now we have to worry about whether or not a
particular vendor is listening and will seek legal recourse based on
an opinion expressed?


Mike Hanson
Network Security Manager
The College of St. Scholastica
Duluth, MN 55811








On Thu, Dec 8, 2011 at 8:42 AM, SCHALIP, MICHAEL<mschalip () cnm edu
<mailto:mschalip () cnm edu>>  wrote:

     Hey Educause…..any thoughts here?



     We come on this discussion group for the free exchange of ideas –
     and THIS is allowed!?



     Wow…..



     *From:* Dennis Meharchand [mailto:dennis () valtx com
     <mailto:dennis () valtx com>]
     *Sent:* Wednesday, December 07, 2011 1:25 PM
     *To:* SCHALIP, MICHAEL
     *Subject:* RE: Michael - Patent Infringement Notice



     Michael,



     I think your response was bad form.

     I am instructing my lawyers to file the first patent infringement
     lawsuit against CNM.



     Let’s see how much of a bad publicity stunt this is.



     Dennis Meharchand

     CEO, Valt.X Technologies Inc.

     Cell: 416-618-4622<tel:416-618-4622>

     Email: dennis () valtx com<mailto:dennis () valtx com>

     Web: www.valtx.com<http://www.valtx.com>



     *From:* The EDUCAUSE Security Constituent Group Listserv
     [mailto:SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>] *On Behalf Of *SCHALIP,
     MICHAEL
     *Sent:* December 7, 2011 9:34 AM
     *To:* SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>
     *Subject:* [Possible Spam] Re: [SECURITY] Deepfreeze on vm's?



     Bad form…..scare tactics…..bad publicity stunt…..how do we get the
     Educause moderator involved??



     *From:* The EDUCAUSE Security Constituent Group Listserv
     [mailto:SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>] *On Behalf Of *Walter Moore
     *Sent:* Wednesday, December 07, 2011 6:54 AM
     *To:* SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>
     *Subject:* Re: [SECURITY] Deepfreeze on vm's?



     You had it right in your first paragraph. Whatever the merits of
     your patent case (and you will have to forgive my skepticism) you
     have no business interjecting it into this discussion.



     On Tue, Dec 6, 2011 at 11:19 PM, Dennis Meharchand
     <dennis () valtx com<mailto:dennis () valtx com>>  wrote:

     This is likely one of those situations where I should just
     continue to shut my mouth until we are already to act but here goes:



     My company Valt.X Technologies owns the patents in this area and
     we intend to enforce our patents in 2012.

     Here’s my advice – if you are using Deep Freeze or any VDI -
     include in your contract that they cover you for Patent Infringement.



     Valt.X has just won its first public tender in Canada – we own
     this area and intend to enforce our intellectual property rights.



     Our position is that Deep Freeze is a blatant copy of Valt.X
     issued patents and that VDI also infringes our patents – we intend
     to sue all infringers.



     Dennis Meharchand

     CEO, Valt.X Technologies Inc.

     Cell: 416-618-4622<tel:416-618-4622>

     Email: dennis () valtx com<mailto:dennis () valtx com>

     Web: www.valtx.com<http://www.valtx.com>



     *From:* The EDUCAUSE Security Constituent Group Listserv
     [mailto:SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>] *On Behalf Of *Brandon Payne
     *Sent:* December 6, 2011 6:01 PM
     *To:* SECURITY () LISTSERV EDUCAUSE EDU
     <mailto:SECURITY () LISTSERV EDUCAUSE EDU>
     *Subject:* [SECURITY] Deepfreeze on vm's?



     We are looking into VDI for all our computer labs. VMware View to
     be exact with WYSE P20 Zero Clients. Roughly about 300 or more
     vm's for all the labs.



     From a virtual standpoint - do you see the need for Faronics
     Deepfreeze on all computer lab vm's? Currently we are using
     Deepfreeze on our desktops in all labs and has worked out great.
     For this situation, I'm not interested in the security
     implications of why Deepfreeze is bad, just if its recommended in
     a virtual environment.



     What are you doing in situations if a user profile gets hosed up
     with malware in this vm enviroment?


     --
     Brandon Payne
     Technical Support Specialist
     Information Services
     Sauk Valley Community College





     --
     +-----------------------------------------------------------------+
     Walter R. Moore --  Sr. Systems Administrator, Eckerd College
     moorewr () eckerd edu<mailto:moorewr () eckerd edu>  --
     http://home.eckerd.edu/~moorewr<http://home.eckerd.edu/%7Emoorewr>

     "It was glorious to see -- if your heart were iron,
     And you could keep from grieving at all the pain" - The Iliad (13.355)

     I'm on twitter: http://twitter.com/moorewreckerd

     ***Reminder! ITS will never ask you to e-mail your password!***


     --
     This message has been scanned for viruses and
     dangerous content by *MailScanner*<http://www.mailscanner.info/>,
     and is
     believed to be clean.


     --
     This message has been scanned for viruses and
     dangerous content by *MailScanner*<http://www.mailscanner.info/>,
     and is
     believed to be clean.


     --
     This message has been scanned for viruses and
     dangerous content by *MailScanner*<http://www.mailscanner.info/>,
     and is
     believed to be clean.


     --
     This message has been scanned for viruses and
     dangerous content by *MailScanner*<http://www.mailscanner.info/>,
     and is
     believed to be clean.





Current thread: