<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>dmiessler.com | grep understanding - Latest Comments in New Study Piece: Zone Transfers</title><link>http://danielrm26.disqus.com/</link><description>dmiessler.com/about/</description><atom:link href="https://danielrm26.disqus.com/new_study_piece_zone_transfers/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 22 Jan 2008 13:32:09 -0000</lastBuildDate><item><title>Re: New Study Piece: Zone Transfers</title><link>http://dmiessler.com/blog/new-study-piece-zone-transfers#comment-4357377</link><description>&lt;p&gt;You should read the decision at &lt;a href="http://www.spamsuite.com/node/351" rel="nofollow noopener" target="_blank" title="http://www.spamsuite.com/node/351"&gt;http://www.spamsuite.com/no...&lt;/a&gt;  I think what may really be in question here is what does and what does not constitute hacking.  Is a port scan hacking?  I guess it depends on the context of which you are using it.  How about running telnet and ssh against each open port you find to see which give you a login prompt?  Is just doing that hacking?  Is there a real-world valid reason you would do so against the average server as a general member of the public?  I don't think so, but is that really hacking and should you be charged with a crime for it?  I'm not really sure.  I would like to see judges error on the side of caution on such matter until legislation can be passed that has caught up with the times though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maxo</dc:creator><pubDate>Tue, 22 Jan 2008 13:32:09 -0000</pubDate></item></channel></rss>