>>20032>1. Can you talk in general what kind of non-trivial C projects you've done?
I would be a little too close to doxing myself if I did that, but it's related to secure communications.
>2. Why Google? Try SearX or ixquick
I'll check both those out.
>3. Any new cool projects you made out of this like that redirector you've mentioned?
I've just been playing around with DNS spoofing the past few days, trying different things and learning about how DNS works. I tried to spoof the DNS request rather than the response (i.e. I drop the target's request, spoof my own request with the same ID, then let the response through to the target), but that doesn't work. I guess the client has to verify that the original request query name matches the query name in the response. My new working method has me doing a single initial DNS request for the "trap" domain, storing the result, and then replacing DNS responses to the target with my stored result while leaving the target's query intact.
I haven't decided what my next project will be yet. I'm thinking maybe a router like >>19920
suggested. I'm also beginning to learn how to use tcpdump alongside/instead of wireshark.
>4. Still going at it with TCPIP illustrated? How beneficial and practical is it
I'm finding it invaluable as a protocol reference, which is exactly what I needed. I've been reading through RFC's as well, but those can be pretty verbose.