void-star

8 ms·

61.
by void-star 10y ago
Can somebody actually comment/back-up the comments about how open or not this effort is? I could see legitimate benefits from this kind of collaboration (it's ultimately about the ability to process data, not the data itself, afte
62.
by void-star 10y ago
buy it anyway. it's for a good cause
63.
by void-star 11y ago
This is so true. It has been a number of years since I worked with either agency doing computer forensic work, but my experience was pretty much the exact same. While SS consistently made a concerted effort to investigate crimes and build a
64.
by void-star 12y ago
As to the second point. This "fiddling" with "miscellaneous" input characters could also be interpreted cover brute-forcing login attempts. I'm not sure that's a good precedent...
65.
by void-star 12y ago
So... FWIW, I totally don't have these problems with twitter. It's probably because I only check my twitter feed and spout out a few tweets at a time once every two weeks or so and pretty much ignore it the rest of the time. Full
66.
by void-star 12y ago
ptrace is actually a more reliable way to get at remote process memory on Android, I think. I'd suspect this before /proc. Also, /proc nor ptrace is "useless". Both are actually fundamental to several aspects of the
67.
by void-star 12y ago
Well... how do you suppose the API gets at all the things? (not everything is done across IPC/binder, much is in process)
68.
by void-star 12y ago
Sorry, this doesn't really address the OP question. But this discussion got me wondering. If Apple's claims that Swift is faster than obj-c actually prove to hold up, would it be possible/worth-it for something like RubyMotio
69.
by void-star 12y ago
There's a term for that. It's called "having a false sense of security".
70.
by void-star 12y ago
You're better off not storing your passphrase in the keychain and just typing it in that one first time, though. But it's still marginally better than an unencrypted private key for automation if you need a 100% unattended setup.
71.
by void-star 12y ago
Yep. The general technique of scraping memory for private keys and certificates a pretty well-known and established. Particularly in forensics and malware circles. I don't point it out to engage in the "who was first" thing.
72.
by void-star 13y ago
Actually, like I said, I didn't even read the rest... so it wasn't an assessment on the article at all. It was an assessment of the author. But here's a job tip: Don't talk about women like this. If you get a job, you wi
73.
by void-star 13y ago
This may very well have been an excellent piece. But, the author lost me no later than 2 sentences in with his immature and sexist "nerdy girl" analogy. I just didn't even bother to read the rest. Working in silicon valley my
74.
by void-star 13y ago
Wireshark dissector plugin? taken down? I haven't really followed wireshark goings-on in a while, but wow... just wow... I don't think i've seen this before: https://github.com/davidgfnet/wireshark-whatsa
75.
by void-star 13y ago
Not exactly. iOS 7+ introduced Cocoa<->Javascript bridging capabilities in the public APIs. Before that, similar iOS APIs had existed as "private" ones (so, very uncommonly used outside of apple's own apps). iOS doesn&#
76.
by void-star 13y ago
Numerous App Store apps contain symlinks around the detached codesignature, most likely caused by changes over the years to the codesignature utility. Also in keeping with Xcode semantics, embedded frameworks often contain symlinks as well.
77.
by void-star 13y ago
Triple boot to iOS and I'll think about it...
78.
by void-star 13y ago
Yea, i'm not sure why they bothered to try to obfuscate the dst address at all, the article mentions siri...
79.
by void-star 13y ago
ProTip: when whiting out your wireshark packet captures, always remember your hexdump: dst=17.130.16.4 $ whois 17.130.16.4 ... NetRange: 17.0.0.0 - 17.255.255.255 CIDR: 17.0.0.0/8 OriginAS: N
80.
by void-star 14y ago
Not trying to bring up a language war or jump on the wagon berating ruby "magic" (so tired of those conversations. I love the dynamic nature of ruby. That said... the code examples in this article are exactly the patterns that were leverage
81.
by void-star 14y ago
agreed. Squash is finely tuned with a set of features to fill in gaps found in another very popular commercial tool in the same vein. tl;dr: don't knock it till you try it!
82.
by void-star 14y ago
pretty good writeup - miss the days when contrived examples were considered a cop-out though ;)
83.
by void-star 14y ago
congrats to bufferbox, and kudos on an excellent slogan: "let us handle your package" <immature snicker>
84.
by void-star 14y ago
Wow ok.. I'm going to try to be polite. I don't think _you_ tried it as you suggest I do: first shot: ~ gcc -o foo -ggdb foo.c foo.c: In function ‘main’: foo.c:31: error: ‘flippedPoint’ undeclared (first use in this function)
85.
by void-star 14y ago
This is really far off, actually. I don't mean to criticize. I think the best advice is to read K&R C again. And, as some other posters have suggested, take a look and at least a passing understanding of the memory model and assembly co
86.
by void-star 14y ago
On the contrary, I think inventing a new class of of "call-by-X" function arguments makes it harder to explain Python to newcomers. I would clarify that I think I'm talking about seasoned programmers, and you probably mean somebody who's a
87.
by void-star 14y ago
This analysis is how I've always understood the distinction between call-by-value or reference. I think the author of the article is a little confused about C++ as well, or perhaps just doesn't have a firm enough handle on it to be able to
88.
by void-star 14y ago
So, if somebody sends this link to Donald Trump and he reads it? Is he responsible for full fines from that point on? I suppose he could actually afford the royalties...
89.
by void-star 14y ago
Good to hear news from OLPC. This is an interesting piece, if a little 'fluff'y.
90.
by void-star 14y ago
I tried iTerm for about a year. After getting fed up watching it lag or crash all the time. I definitely went back to stock Terminal and haven't looked back.

More ›