EvilZone

https://evilzone.org/wiki//index.php/Main_Page
www.google.com


Fucking seriously?

I feel like he was asking what ebooks on "hacking" are worth reading, not where to find a huge list of ebooks, or a comprehensive guide to searching for them.  Plenty of books you find will try to be too generic or entry-level imo.  For instance, I've read some books with a title like "advanced low level exploitation" or something, and then you turn to chapter 1 and they're explaining what assembler is... At that point I am almost positive the book is going to be a waste of time.  It may not be, but more often than not, its outdated and/or too much "intro". 

We've discussed this in IRC a few times and some very knowledgeable people have chimed in.  OP should also note that it depends on what you're trying to read about.  If you're wanting to learn about windows internals, then the classic "Windows Internals 6th Edition" is good to at least have around, even if it's not the easiest to read front-to-back (who would've known...)  If you're doing a wargame or something and you need to exploit a format string vuln or something similarly specific, google around some of the well-known hacking zines.  Phrack comes to mind when it comes to low level shit. 

Once you get to a point where you're tired of the basics, try and focus in on something like buffer overflows, and look up ways to defeat certain modern-day protections, imo you won't find these in a book because of how specific it is to the software/situation, you'll find more info through articles and writeups you can find online.  Idk, maybe I'm full of shit and this adderall is just getting to me, but I've gone pretty far off-topic but the tl;dr is sometimes the best learning materials aren't in the form of books, because a lot of them kind of suck.

Well I'm glad you caught the hint that we won't guide you through and post unique and individualized replies for every repost of the same beginner question. If you have a question on something specific or unique my reply would have been different. But instead its a question that gets asked over and over. Just read the stickies and you'll do fine.

Lol seriously though, seems these packet crafting posts are pretty popular (techb/rba u da reel mvps), maybe once alpha is live someone can copy and paste them all in their own board?  Like a network-hacking-script-snippets-sub-board-thing  or something?

Well, as much as I hate to admit it , you're correct about sizeof(char), it's definitely equal to one according to the standard.*  I see what you mean about the chkret macro now, not freeing what it should, good catch.

*I took some time to do a little more research into the subject and even if a "char" is 32 bits, sizeof(char) will always return 1.  You can also find the number of bits contained in a char by looking at CHAR_BITS in <limits.h>. Source: (ctrl+f) for section 6.5.3.4

Um, nexus 5 owner here, this is totally new information to me lol. Thanks for sharing m8 +1

So this is actually a pretty old project of mine, I wrote it on a whim and liked the way it turned out.  I'm a big fan of chaining simple programs together (or I'm using that as my excuse  ) to accomplish a more complex task.  I was also inspired to post this from ca0s' crypter post which as far as I know, also impliments a simple xor 'encryption'.  Anyways, here's the code circa early April 2015.

#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/stat.h>

#define KEY 0x2e
#define xor(x) ((((x) >= 0) && ((x) <= 255)) ? ((x) ^= KEY) : ((x) = 0))
#define chkret(func, var) \
        if (!(var)) { \
            fprintf(stderr, func " has failed.\n"); \
            return -1; \
        }

unsigned char *bptr;

size_t fsize(const char *fn);
int bpull(FILE *fp, unsigned char *b, const char *fn, size_t s);

int main(int argc, char *argv[]) {
    char *fn;
    FILE *fp;
    int r;
    size_t s, i;

    if (argc != 2) {
        fprintf(stderr, "Usage: ./xcat <file>\n");
        return -1;
    }

    /* the chkret(func, var) macro checks if the return value of each
     * function is zero.  If it isn't, then we return(-1);  The idea was
     * to cut down on some of the "if" statement clutter that xcat was
     * suffering from checking return values manually. */
    fn = argv[1];
    s = fsize(fn);
    chkret("fsize", s);

    fp = fopen(fn, "rb");
    chkret("fopen", fp);

    bptr = malloc(sizeof(unsigned char) * s);
    chkret("malloc", bptr);

    r = bpull(fp, bptr, fn, s);
    chkret("bpull", r);

    for(i = 0; i < s; ++i)
        xor(bptr[i]);

    /* make this a user specified fp in the future? I like this
     * functionality */
    fwrite(bptr, 1, s, stdout);

    fclose(fp);
    free(bptr);
    bptr = NULL;

    return 0;
}

size_t fsize(const char *fn) {
    struct stat st;
    return (stat(fn, &st) == 0) ? st.st_size : 0;
}

int bpull(FILE *fp, unsigned char *b, const char *fn, size_t s) {
    return ((s-1) == fread(b, sizeof(unsigned char), s, fp)) ? 0 : -1;
}


This looks interesting, I'll probably watch it.  If I can handle watching all one and a half hours of ALGORITHM, and enjoy it, then I bet I can make it through this .