carlf
commented
8 years ago I'm getting this from edebug:
Debugger entered--Lisp error: (void-variable url-http-response-status)
apply(debug error (void-variable url-http-response-status))
edebug(error (void-variable url-http-response-status))
url-http-parse-headers()
url-http-chunked-encoding-after-change-function(107256 110836 3580)
url-http-generic-filter(#<process krebsonsecurity.com> " with information and security resources to individuals who may have been affected. The security of our networks is our top priority and we are acting accordingly.”</p>\n<p>“The few employees who may have been affected were notified promptly, and at this point the impact appears to be quite small.”</p></blockquote>\n<p>According to a LANDESK employee who spoke on condition of anonymity, the breach was discovered quite recently, but system logs show the attackers <em>first broke into LANDESK’s network 17 months ago, in June 2014</em>.</p>\n<p>The employee, we’ll call him “John,” said the company only noticed the intrusion when several co-workers started complaining of slow Internet speeds. A LANDESK software developer later found that someone in the IT\302\240department had been logging into his build server, so he asked them about it. The IT department said it knew nothing of the issue.<span id=\"more-33029\"></span></p>\n<p>John said further investigation showed that the attackers were able to compromise the passwords of the global IT director in Utah and another domain administrator from China.</p>\n<p>“LANDESK has found remnants of text files with lists of source code and build servers that the attackers compiled,” John said. “They know for a fact that the attackers have been slowly [archiving] data from the build and source code servers, uploading it to LANDESK’s web servers, and downloading it.”</p>\n<p>The implications are potentially far reaching. This breach happened more than a year and a half ago, during which time several versions and fixes of LANDESK software have been released. LANDESK has thousands of customers in all areas of commerce. By compromising LANDESK and embedding a back door directly in their source code, the attackers could have access to large number of\302\240computers and servers worldwide.</p>\n<p>The wholesale theft of LANDESK source code also could make it easier\302\240for malware and exploit developers to find security vulnerabilities in the company’s software.</p>\n<p>A LANDESK spokesperson would neither confirm nor deny the date of the breach or the source code theft, saying only that the investigation into the breach is ongoing and that the company “won’t comment on speculation.”</p>\n<p><strong>Update, 6:51 p.m. ET: </strong>Landesk just posted <a href=\"https://community.landesk.com/support/docs/DOC-39460\" target=\"_blank\">a statement</a> on its support site. The relevant bit is here: “Given the recent online speculation about the security of our product, we want to reassure you about the security of our products and provide some best practices to help you increase your security posture if needed.\302\240 We can\342\200\231t comment on the specifics of the investigation, but based on the information we know so far, we have not confirmed a risk to our customers\342\200\231 environments, and there are no known primary attack vectors using LANDESK software.”</p>\n]]></content:encoded>\n <wfw:commentRss>https://krebsonsecurity.com/2015/11/breach-at-it-automation-firm-landesk/feed/</wfw:commentRss>\n <slash:comments>59</slash:comments>\n </item>\n </channel>\n</rss>\n
\n<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/
\n
\nPage Caching using memcached
\nDatabase Caching 1/5 queries in 0.001 seconds using memcached
\nObject Caching 782/787 objects using memcached
\n
\n Served from: krebsonsecurity.com @ 2015-12-16 01:18:13 by W3 Total Cache -->
\n0
\n
\n- Peer has closed the GnuTLS connection\n")
recursive-edit()
edebug--recursive-edit(after)
edebug--display([t 0 0 10000 nil url-queue-run-queue nil idle 0] 1 after)
edebug-debugger(1 after [t 0 0 10000 nil url-queue-run-queue nil idle 0])
edebug-after(0 1 [t 0 0 10000 nil url-queue-run-queue nil idle 0])
(lambda nil (edebug-after (edebug-before 0) 1 (elfeed-update-feed "https://krebsonsecurity.com/feed/")))()
edebug-enter(edebug-anon90501 nil (lambda nil (edebug-after (edebug-before 0) 1 (elfeed-update-feed "https://krebsonsecurity.com/feed/"))))
edebug-enter(edebug-anon90501 nil (lambda nil (edebug-after (edebug-before 0) 1 (elfeed-update-feed "https://krebsonsecurity.com/feed/"))))
eval((edebug-enter (quote edebug-anon90501) nil (function (lambda nil (edebug-after (edebug-before 0) 1 (elfeed-update-feed "https://krebsonsecurity.com/feed/"))))) nil)
eval-expression((edebug-enter (quote edebug-anon90501) nil (function (lambda nil (edebug-after (edebug-before 0) 1 (elfeed-update-feed "https://krebsonsecurity.com/feed/"))))))
edebug-defun()
#<subr call-interactively>(edebug-defun record nil)
ad-Advice-call-interactively(#<subr call-interactively> edebug-defun record nil)
apply(ad-Advice-call-interactively #<subr call-interactively> (edebug-defun record nil))
call-interactively(edebug-defun record nil)
command-execute(edebug-defun record)
helm-M-x(nil "edebug-defun")
#<subr call-interactively>(helm-M-x nil nil)
ad-Advice-call-interactively(#<subr call-interactively> helm-M-x nil nil)
apply(ad-Advice-call-interactively #<subr call-interactively> (helm-M-x nil nil))
call-interactively(helm-M-x nil nil)
command-execute(helm-M-x)
skeeto
I'm getting an error on http://krebsonsecurity.com/feed/. The W3C validator says it is valid and I get what appears to be valid XML when I curl it but elfeed is giving me:
Elfeed parse failed for https://krebsonsecurity.com/feed/: (error XML: (Not Well-Formed) Only one root tag allowed)
Any hints?