Comments for onelittlewindow

Comment on Shmoocon 2008 — the “not sexy” talks part II by Ba?amel Soslu Patates Tarifi

Ba?amel Soslu Patates Tarifi — Tue, 08 May 2012 03:31:40 +0000

I’ve recently started a web site, the information you provide on this web site has helped me tremendously. Thanks for all of your time & work.

Comment on In the news today by Rachael Ness

Rachael Ness — Sat, 05 May 2012 14:37:51 +0000

The best of all the Star Treks? Well it certainly isnt Enterprise!

Comment on Hello World? by empuje de publicidad

empuje de publicidad — Wed, 25 Apr 2012 00:50:03 +0000

excellent article, i certainly love this web site, keep it.

Comment on Blog Reboot, as well. by Frank

Frank — Sat, 18 Feb 2012 14:13:50 +0000

I always enjoy a well written blog post, even more when it’s someone I know (possibly because so few do so), or would like to know.

It can be difficult for people who work in “non-creative” fields to break the routine of cause:effect and let go to create something that has no direct action (or seems so.) As you point out, there seems to be so much “said” by those with nothing to say that it seems like folly to add your own voice; as Twain said: if one argues with a fool, an outside observer may not be able to tell the difference. This is a regular internal dialogue here as well.

As for ego, I don’t know that we don’t leave some of that stuck to anything we create; I think that’s how one knows what the creator cares about. I’ve come to realize that no one can be more critical of me than me, which took some time, so even if (especially if?) your writing is only for yourself, you’ll be well off; if you find an audience, that is a bonus.

Good writing has lead me to understand all sort of people, ideas, and subjects I never considered before, even if ultimately it only tells me about the author. I wish you luck in this endeavor, and look forward to more as it comes.

Comment on Nmap for Conficker by martin

martin — Mon, 29 Mar 2010 08:16:13 +0000

Can you help with the new smb-check-vulns.nse script? It seems that it has changed a bit and they are now writing the results to a table before outputing.. I tried adding the code you suggested in various places but keep getting errors.. below is the excerpt from version 5.21.
— Check for Conficker
status, result = check_conficker(host)
local hosttodump = host.ip
if(status == false) then
local msg = CONFICKER_ERROR_HELP[result] or “UNKNOWN; got error ” .. result
table.insert(response, get_response(“Conficker”, msg, nil, 1)) — Only set verbosity for this, since it might be an error or it might be UNKNOWN
else
if(result == CLEAN) then
table.insert(response, get_response(“Conficker”, “Likely CLEAN”, nil, 1))
elseif(result == INFECTED) then
table.insert(response, get_response(“Conficker”, “Likely INFECTED”, “by Conficker.C or lower”, 0))
elseif(result == INFECTED2) then
table.insert(response, get_response(“Conficker”, “Likely INFECTED”, “by Conficker.D or higher”, 0))
else
table.insert(response, get_response(“Conficker”, “UNKNOWN”, result, 0, 1))
end
end

Comment on Account Collision on Twitter? by Doug Wilson

Doug Wilson — Thu, 23 Apr 2009 20:27:48 +0000

Well, “data inconsistencies” definitely could be the cause of the problem. Honestly, the issues that I’ve seen are a little more severe than what they’ve outlined. Ah well, hopefully this will clear it up, and they (internally) are more aware of what’s going on than they’ve indicated.

Comment on Account Collision on Twitter? by Jeremy

Jeremy — Thu, 23 Apr 2009 20:23:01 +0000

I agree with you Doug, that this is a big issue. I’ve just found out that Twitter has posted a status update on their website, which seems to be concerning this issue, although its a little vague:

http://status.twitter.com/post/99180872/tracking-down-data-inconsistencies

Comment on Account Collision on Twitter? by Doug Wilson

Doug Wilson — Thu, 23 Apr 2009 20:09:57 +0000

I think that it is being corrected over time. I have never actually gotten in touch with Twitter support on the issue — I researched it until late last night, and then this morning, it was “fixed.”

Whether this is their application catching up with itself, or if they are manually fixing something that is getting out of control is unknown. My concern is that having account collisions across a service is kind of a big deal — you really can’t trust a service if your risking regularly having other people’s information show up as your own, or get locked out of your account due to wires being crossed.

Obviously, Twitter is a free service, but like Gmail, its has unrealistic expectations put on it due to the vast scope and impact that its service has. I’ll be curious to see if they make a public statement about the issue, or if it’s just chalked up as another technical problem that twitter has so often.

Comment on Account Collision on Twitter? by RT: @Fenng: http://onelittlewi… « ?????

RT: @Fenng: http://onelittlewi… « ????? — Thu, 23 Apr 2009 18:03:24 +0000

[...] @Fenng: http://onelittlewindow.org/blog/?p=228 – new accounts on twitter are being taken over by [...]

Comment on Account Collision on Twitter? by Jeremy

Jeremy — Thu, 23 Apr 2009 17:37:28 +0000

Doug, thanks for the answer. I’ve noticed other people with the same issue are getting back control over their accounts. And so did you. Did this happen by itself, or was it a manual correction by Twitter?

I’m just wondering. If there somehow is a “lag” during which the problems are solved automatically, all I have to do is wait I guess.