{"id":15522,"date":"2007-12-28T17:50:02","date_gmt":"2007-12-28T17:50:02","guid":{"rendered":"http:\/\/blogs.adobe.com\/jnackdev\/2007\/12\/whats-with-adobe-the-shady-server-name.html"},"modified":"2007-12-28T17:50:02","modified_gmt":"2007-12-28T17:50:02","slug":"whats_with_adobe_the_shady_server_name-2","status":"publish","type":"post","link":"https:\/\/jnack.com\/blog\/2007\/12\/28\/whats_with_adobe_the_shady_server_name-2\/","title":{"rendered":"What&#039;s with Adobe &amp; the shady server name?"},"content":{"rendered":"<p>Thanks for all the feedback on <a href=\"http:\/\/blogs.adobe.com\/jnack\/2007\/12\/adobe_ate_me_ba.html\">this morning&#8217;s post<\/a> about Adobe, Omniture, and (non) spyware in CS3. <\/p>\n<p>In truth, <u>I think I did miss a key point<\/u>:  in this instance the objections seem to center not so much on whether Adobe apps are contacting a server, but rather that the server is named &#8220;192.168.112.2O7.net,&#8221; rather than something obvious and communicative like &#8220;adobestats.omniture.com.&#8221;&#160; People are rightly asking why that is, and unfortunately I don&#8217;t know the answer.&#160; I&#8217;m way out of my depth on the details of IP addresses, ports, etc., so I hesitate to comment further.<\/p>\n<p>Instead I&#8217;ll work on getting some details from people with more expertise.&#160; Given where we are in the holiday period, it may take a little time.&#160; I&#8217;ll post more info as&#160;I get it.&#160; Thanks for your patience.<\/p>\n<p>This is a great example of why I said that &#8220;<u>Adobe could and should do a better job taking security concerns into account<\/u>.&#8221;&#160; Even if an application&#8217;s behavior is ultimately innocuous, it&#8217;s important to be transparent and forthcoming about what&#8217;s going on.&#160; I don&#8217;t want software sneaking around behind my back any more than the next guy does, and Adobe (like all companies) needs to make sure it&#8217;s not abusing users&#8217; trust. \n<\/p>\n<p>[<b>Update<\/b>: I posted updates <a href=\"http:\/\/blogs.adobe.com\/jnack\/2008\/01\/what_data_do_ad.html\">here<\/a> and <a href=\"http:\/\/blogs.adobe.com\/jnack\/2008\/01\/adobe_and_omnit.html\">here<\/a>.  The complete set of posts is <a href=\"http:\/\/blogs.adobe.com\/jnack\/privacy_spyware\/\">here<\/a>.]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thanks for all the feedback on this morning&#8217;s post about Adobe, Omniture, and (non) spyware in CS3. In truth, I think I did miss a key point: in this instance the objections seem to center not so much on whether Adobe apps are contacting a server, but rather that the server is named &#8220;192.168.112.2O7.net,&#8221; rather [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[46],"tags":[],"_links":{"self":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/15522"}],"collection":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=15522"}],"version-history":[{"count":0,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/15522\/revisions"}],"wp:attachment":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=15522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=15522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=15522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}