{"id":497,"date":"2003-12-10T00:00:00","date_gmt":"2003-12-10T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/12\/10\/sco-hit-again-by-dos-attack\/"},"modified":"2021-12-30T11:37:29","modified_gmt":"2021-12-30T11:37:29","slug":"sco-hit-again-by-dos-attack","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/12\/10\/sco-hit-again-by-dos-attack\/","title":{"rendered":"SCO hit again by DoS attack"},"content":{"rendered":"<p>The SCO Group&#8217;s website has been knocked out of service by a denial-of-service (DoS) attack.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The attack began at 11:20am GMT Tuesday, shutting down the company&#8217;s main [url=http:\/\/www.sco.com]www.sco.com[\/url] website, according to company spokesman Blake Stowell.  SCO has raised the ire of the open-source community by claiming that the Linux operating system contains software that violates SCO&#8217;s intellectual property.<\/p>\n<p>More info: [url=http:\/\/www.computerweekly.com\/articles\/article.asp?liArticleID=127156&#038;liFlavourID=1&#038;sp=1]http:\/\/www.computerweekly.com\/articles\/article.asp?liArticleID=127156&#038;liFlavourID=1&#038;sp=1[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-497","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/497","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=497"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/497\/revisions"}],"predecessor-version":[{"id":2984,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/497\/revisions\/2984"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}