greystatic

Members
  • Content count

    149
  • Joined

  • Last visited

Community Reputation

0 Neutral

About greystatic

  • Rank
    mad 1337

Contact Methods

  • Website URL
    http://
  • ICQ
    233105250
  1. http://phrack.org/unoffical/
  2. yes, integers are 4 bytes on most 32-bit platforms. what does that have to do with this? /me confused
  3. if the size of whatever you are to hold in the string is fixed, only declare the array as such. if the size of what you're storing in the string is dynamic, use dynamic memory allocation, see malloc(3) and friends. ..there's no need to overshoot yourself. It's sloppy and dangerous. (all assuming you're talking either about C or C++ w/o stl shit)
  4. login as a different user, SHELL=/bin/bash sudo -s, chsh /bin/bash
  5. I really wouldn't recommend a scripting language for brute-forcing anything. MD5 and sha1 are hashes, not ciphers. Base64 isn't either, it's just an encoding scheme that takes any data, and converts it into portable ascii at the cost of ~33% bloatage. As far as the original questions go "hashes for different encryption routines" eh? Anything that is stored for pass. auth will probably not be truncated for security reasons, and if it is it would be have to be a system that stores hashes, as you couldn't conceivably do this with ciphertext.. [edit] fixed reply to misread part
  6. ~/.xinitrc It sounds like you currently don't have one, create it if it doesn't exist. Just add startkde to it, eg $ echo startkde > ~/.xinitrc note that the above will clobber it, it doesn't sound as if you have anything you wish to keep in there though.
  7. The proper way to load a wm is to add the command to start your wm to either your ~/.xinitrc or the system wide xinitrc.
  8. http://www.phrack.org/ Not in print of course (unless you're lucky enough to get to ruxcon), but by far the best source of quality information.
  9. It can't find a C compiler. Get a gcc binary for whatever package system your distro uses. You might want to explain yourself a bit more though, I'm very confused.
  10. WEP is pretty much useless if you're interested in security (probably prevent a casual attacker though). I'd look into IPSec. It's worth the trouble imo. --> http://www.binrev.com/forums/index.php?showtopic=3081
  11. yeah, 'cept like I said, the code won't compile on in windows. That is not necessarily true at all. Without seeing the code, we don't know if it uses proprietary *NIX system calls. If it is standard ANSI C then is is completely portable. ANSI C is a standard for C language syntax/features and a minimalistic standard library, not system calls / full-fledged libc interaction etc etc. As for the standard library, C99 defines assert.h, complex.h, ctype.h, errno.h, fenv.h, float.h, inttypes.h, iso646.h, limits.h, locale.h, math.h, setjmp.h, signal.h, stdarg.h, stdbool.h, stddef.h, stdio.h, stdlib.h, string.h, tgmath.h, time.h, wchar.h, wctype.h Anything but the most basic of programs are going to use much more, it is safe to assume that most things are not windows <--> nix compatible without making that an explicit goal. [edit] I'm an idiot, fixed incorrect information.
  12. definately a good point. aren't there bootable "forensics" distros that do similar things? Yup. The forensics live cds do a whole shitload, but for this specific purpose, they accomplish the same goal a bit better (eg, lkm rootkits are not a consideration) at the cost of convenience. I find just doing small things like this that can be done while the system is running is a nice compromise, for my purposes at least.
  13. It's fairly pointless to use chkrootkit unless you're taking measures to protect the integrity of the chkrootkit script and all of the other things it depends on. Even if you use a system-wide integrity checker like tripwire, aide, yafic, etc, you still have a (security) dependency that you could eliminate. So I always thought it would be best to gather up chkrootkit and all of it's dependencies, make sure any executables are statically linked, and stick it on read-only media (such as a cd-r). All of the executables on the iso I threw together today are: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, statically linked, stripped You can get the iso, along with a pgp sig and md5/sha1 hashes of it at http://abitsqueamish.org/bitbin/chkrootkitcd/. use: /path/to/cd/chkrootkit -p /path/to/cd ...and none of this shit is extensively tested, all I can confirm is that it works on my system, and that static linking looks sane (tried it in a chroot jail). Hope somebody gets some use out of it.
  14. Are you in the wheel group? If not, add yourself to the wheel group by editing /etc/group, see group(5) for details.
  15. Are you aware of the BSD license and what it allows? Also, just as an tangible example that I remember seeing somewhere, take a look at the strings in the windows xp ftp.exe. You'll see a BSD copyright notice. [edit] and.. why the fuck would a copyright notice be a string constant? I would think they would attribute copyright in the form of a comment... *shrug* [edit2] removed massive inline quote