DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
valhalla has quit [Ping timeout: 246 seconds]
lekernel has quit [Quit: Leaving]
wej has quit [Ping timeout: 260 seconds]
wej has joined #qi-hardware
valhalla has joined #qi-hardware
valhalla has quit [Ping timeout: 272 seconds]
valhalla has joined #qi-hardware
valhalla has quit [Ping timeout: 264 seconds]
valhalla has joined #qi-hardware
FDCX has quit [Read error: Operation timed out]
<wpwrak> but let's rewrite this as "identified, questioned and ... terminated with extreme prejudice" ;-)
FDCX has joined #qi-hardware
pcercuei has quit [Ping timeout: 252 seconds]
kristianpaul has quit [Ping timeout: 246 seconds]
wej has quit [Ping timeout: 264 seconds]
dos1 has quit [Ping timeout: 252 seconds]
porchaso0 has joined #qi-hardware
porchao has quit [Ping timeout: 248 seconds]
bzb_ has joined #qi-hardware
bzb has quit [Ping timeout: 252 seconds]
lilvinz- has joined #qi-hardware
lilvinz has quit [Ping timeout: 248 seconds]
wpwrak has quit [Ping timeout: 248 seconds]
wpwrak has joined #qi-hardware
bzb__ has joined #qi-hardware
bzb_ has quit [Ping timeout: 245 seconds]
bzb__ has quit [Ping timeout: 245 seconds]
bzb has joined #qi-hardware
viric has quit [Remote host closed the connection]
viric has joined #qi-hardware
porchaso0 has quit [Read error: Connection reset by peer]
porchao has joined #qi-hardware
bzb has quit [Ping timeout: 245 seconds]
bzb has joined #qi-hardware
bzb has quit [Quit: I hate to quit but my bladder's full. :-(]
wolfspraul has joined #qi-hardware
<whitequark> > If you've been cleared and especially if you've been polygraphed, you're an insider and you are presumed to be trustworthy
<whitequark> polygraphed. yeah. because that means something. :/
jekhor has joined #qi-hardware
<wpwrak> perhaps a security clearance shouldn't only involve background checks, polygraph, and all that, but also an IQ test ...
<wpwrak> or maybe it is that their internal bureaucracy is so horrible that sharing passwords is part of the daily routine just to get things done
<whitequark> (IQ test) not higher than X? :)
<wpwrak> yeah, finding the right range may be tricky :) make them too smart and you get a lot more snowdens :)
lekernel has joined #qi-hardware
<kyak> "They have emphatically denied that he provided any classified material to countries such as China or Russia."
<kyak> oh, that's really important!
<kyak> like, yeah, we fucked up, but not that bad!
<kyak> i wonder, how many of these 25 employees were women?
<kyak> 24.5
<kyak> he good!
<larsc> well, the trick to get passwords is to not just outright ask for them, but let the person come to you with a problem (which you might have created), and then say in order to fix the problem you need to password
<larsc> or something like, 'It will at least take two weeks to restore your E-Mail access' 'Isn't there a way to speed this up' 'Yea, but it's not exactly by the book' ...
<kyak> you sound like an experienced social engineer :)
<larsc> I think that's elementary stuff
wej has joined #qi-hardware
<kyak> for an experienced social engineer, yes ^) but not for those 25 employees
<wpwrak> we worked as an admin, so people may have come to him with problems on a regular basis
<wpwrak> but still, you'd expect that proper password procedures would be about the first thing they teach people at this sort of places
<wpwrak> s/we /he / # oops, now i'm on their list :)
wej has quit [Ping timeout: 260 seconds]
wej has joined #qi-hardware
<larsc> but not giving him the password would be like saying 'I think you are up to something.'
<larsc> and that would be rude since he offered to help them
<whitequark> well, isn't that *why* you should not give people passwords?
<whitequark> because they well may be up to something.
<whitequark> and the help he provides is his job
<larsc> nah, but if you say something like I can restore your email account in two hours instead of two weeks
<whitequark> well, there's a difference between rude and inconvenient to you
<larsc> well the incovenience is another factor in that situation as well
<larsc> but the basic situation you want to engineer is a situation where the person would feel unconmfortable not to give you their password
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
mth has quit []
bzb has joined #qi-hardware
wej has quit [Ping timeout: 260 seconds]
wolfspraul has quit [Ping timeout: 245 seconds]
jekhor has quit [Quit: Leaving]
wolfspraul has joined #qi-hardware
jekhor has joined #qi-hardware
bzb has quit [Quit: I hate to quit but my bladder's full. :-(]
wej has joined #qi-hardware
<DocScrutinizer05> social engineering for noobs
<DocScrutinizer05> :-)
<DocScrutinizer05> that's really the 101 they teach you even in company wide security audits
<DocScrutinizer05> or rather in preparation for...
<DocScrutinizer05> the standard user has no idea why (s)he needs passwords at all, after all it's already HIM/HER who's sitting at the terminal and typing it, so why the additional hassle ;-P
<DocScrutinizer05> and admins considered almighty (which usually they actually are), so all a user might wonder is "why he even needs my password? I'd hope for him to tell *me* my password once I forgot"
<DocScrutinizer05> ~bofh
<DocScrutinizer05> err
<DocScrutinizer05> tried to suggest a good read, but you don't like the bot, so google for it!
wej has quit [Ping timeout: 260 seconds]
wej has joined #qi-hardware
pcercuei has joined #qi-hardware
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
wej has quit [Ping timeout: 260 seconds]
wolfspraul has quit [Ping timeout: 248 seconds]
wolfspraul has joined #qi-hardware
jekhor has quit [Read error: Operation timed out]
<wpwrak> larsc: all very well, but don't forget that this is an area where people have all sorts of security clearances, operate on a need to know basis, where access is compartmentalized, and so on. being paranoid is their foremost obligation.
<wpwrak> DocScrutinizer05: bofh, the great classic ;-)
<DocScrutinizer05> sure ;-)
<DocScrutinizer05> you can learn a lot about social engineering from it
<wpwrak> larsc: that doesn't mean that there can't be a few gullible victims. but that he can go through "20-25" people, who all have elevated access privileges, and that doesn't even raise any suspicion is more than surprising.
<wpwrak> their default attitude should be "you don't need to know my password and i'll inform your superior". now, he may be able to worm his way around the latter "oh, sorry, i'm new here, we always did that at my old job" etc. but the odds should be heavily stacked against this sort of stunt.
<wpwrak> of course, if it turns out that some did inform on him and his (NSA) supervisor didn't pay attention, then i wouldn't want to be in his skin :)
<DocScrutinizer05> now you got to the fun aspects of my daily duty as maemo admin superviser ;-P
<wpwrak> are the maemo admins leaking lots of dirty laundry labeled "top secret" ? :)
<DocScrutinizer05> or should I say senior admin and coordinator?
<DocScrutinizer05> nah, only handling a database with ~90k valuable user data
<DocScrutinizer05> and all that without any paperwork that would establish any form of liability
<DocScrutinizer05> since, you know... community
<DocScrutinizer05> you can't even dream of the flames I receive sometimes
<wpwrak> the more informal, the better the flames ;-)
<DocScrutinizer05> indeed
<DocScrutinizer05> you can't fire volunteers
<DocScrutinizer05> and some you can't even kick since otherwise community will kick you
dos1 has joined #qi-hardware
<DocScrutinizer05> one dude already asked Hildon Foundation to expel me from maemo admin since I dared to overrule him on a security issue
<DocScrutinizer05> where my decision was to the safe side
<DocScrutinizer05> while the dude was rushing all over our infra, abusing his privileges and not communicating what he does, and opened up security bandaid blocks we established when we found a massive vulnerability
<DocScrutinizer05> particularly he re-enabled login to maemo midgard when all users had admin permissions on midgard due to a config fsckup
<wpwrak> well, let him run wild for a while, let him build up a reputation of being an asshole. wait until he makes a big mistake. then pounce :)
<DocScrutinizer05> he DID make a big mistake, I blamed him in closed channel and when another honorable guy asked him to chill a bit he ragequit and never been seen again
jekhor has joined #qi-hardware
<wpwrak> and always remember, there is the common sociopath, there are big sociopath, and there are efficient sociopaths. you want to be the latter :)
<DocScrutinizer05> hi dos1
<wpwrak> DocScrutinizer05: (ragequit) perfect. so it worked as planned :)
<DocScrutinizer05> basically yes
<DocScrutinizer05> for sure I'd rather see him adjust his attitude and behavior
<DocScrutinizer05> particularly since he been partially quite knowledgeable
<DocScrutinizer05> but he been unable to grok the principle of limited permissions
<wpwrak> some people are just looking for a fight. better to be rid of them.
<DocScrutinizer05> he was looking for proving own awesomeness
<DocScrutinizer05> by doing everything on root permissions without peer review or any feedback or permission
<DocScrutinizer05> solitaire
<DocScrutinizer05> no team player
<dos1> DocScrutinizer05: hello!
<DocScrutinizer05> :)
<DocScrutinizer05> wpwrak: basically he maintained a 12VM server infra with 90k users and 10 admins like his own PC at home
<DocScrutinizer05> nobody had (or has) a friggin clue what he did, or why
<wpwrak> ah, now i see why you'd have liked to keep him. someone who single-handedly juggles 12 servers is hard to find.
<DocScrutinizer05> yeah
<wpwrak> yeah, that's the normal case with those guru admins
<DocScrutinizer05> :-P
<DocScrutinizer05> so in the end we are better off without him
<DocScrutinizer05> I told him "you're not supposed to do this. It's an abuse of your privileges, and it's a mega security breach opening up a huge (and known) vulnerability. Please INSTANTLY revert what you did - whaever it been - then reboot the machines where you did changes! INSTANTLY, NOW! THEN we discuss the issue" - he answered by calling me names
<DocScrutinizer05> when *I* did what I asked HIM to do, he asked for my expel
<roh> somebody who takes user data privacy not serious should be sued, not hired.
<DocScrutinizer05> roh: the problem is: we don't hire in community, we don't have funds to hire
<roh> DocScrutinizer05: doesnt matter.
<DocScrutinizer05> sure
<roh> the law doesnt differenciate if you get money or not for doing the work. either do it properly or gtfo
<DocScrutinizer05> well, he's gone and his accounts blocked
<DocScrutinizer05> my mistake - I thought the dude was susceptible to good reasoning and policies to agree upon
<DocScrutinizer05> it turned out he wasn't
<DocScrutinizer05> he received root permissions under the policy to NOT abuse them for ANY editing
<DocScrutinizer05> since our infra been fsckdup in that regard back when
<DocScrutinizer05> (no ACL for example)
<DocScrutinizer05> he abused those permissions in best intent to "fix stuff", but the way he did been causing more havoc than good
bzb has joined #qi-hardware
jekhor has quit [Ping timeout: 252 seconds]
jekhor has joined #qi-hardware
viric has quit [Ping timeout: 240 seconds]
jekhor has quit [Ping timeout: 248 seconds]
viric has joined #qi-hardware
jekhor has joined #qi-hardware
rz2k has joined #qi-hardware
kristianpaul has joined #qi-hardware
lekernel has quit [Quit: Leaving]
Chuck174 has joined #qi-hardware
<Chuck174> if i have 2x4gb ram , should i add my older ram(2x2gb) in the other slot?
Chuck174 has quit [Quit: irc2go]
rz2k has quit []
wolfspraul has quit [Ping timeout: 272 seconds]
wolfspraul has joined #qi-hardware
kilae has joined #qi-hardware
jekhor has quit [Read error: Connection reset by peer]
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 25.0/20131025151332]]
wolfspraul has quit [Ping timeout: 245 seconds]
qwebirc65159 has joined #qi-hardware
qwebirc65159 has quit [Client Quit]