Thread: Trouble with memory flood

  1. #1
    Registered User
    Join Date
    Jul 2005
    Posts
    12

    Trouble with memory flood

    Over the last few days I've been designing and implementing an algorithm to brute force windows passwords.

    That statement feels like it needs qualification. All I can give is that I could download a dozen of these with much more ease if my interest were to use them maliciously. I'm looking to understand how the algorithms work, and how they're implemented in the real world.

    If you're still reading, perhaps you haven't written me off as a script kiddie. I'm flattered. My problem is not with the algorithm or the logon itself (that all works) but when many CreateProcessWithLogonW()'s are executed in the same program inside a loop, an SVCHOST.EXE is launched and continues to take up more and more space (as does my executable).

    So I'm wondering if there's a way to kill the allocated memory during the loop so my program doesn't bloat itself to death.

    Thanks for your time.

  2. #2
    (?<!re)tired Mario F.'s Avatar
    Join Date
    May 2006
    Location
    Ireland
    Posts
    8,446
    Independently of the reasons behind, you surely don't expect anyone in here to help you with this information when you made the objective so clear.

    I do salute you being forward. However, it doesn't hide the fact that you are trying to do something that while not illegal, is highly frowned upon. Besides... it's a silly (read useless) exercise that of trying a brute force attempt at a windows logon screen.

    I don't know the answer to your questions. Windows programming is beyond my abilities. I just hope you don't get it here.
    Originally Posted by brewbuck:
    Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.

  3. #3
    Registered User
    Join Date
    Aug 2001
    Posts
    244
    oops, hehe, post removed
    Last edited by Raven Arkadon; 07-17-2006 at 06:36 PM.
    signature under construction

  4. #4
    pwns nooblars
    Join Date
    Oct 2005
    Location
    Portland, Or
    Posts
    1,094
    How about 'cause it is against cboard policy... post reported.

  5. #5
    Registered User
    Join Date
    Jul 2005
    Posts
    12
    I understand your reasoning, Mario, but if real programmers don't study these things then they'll just keep getting exploited. I looked on google for some time about it, unsuccessfully, and figured that rather than recreating the problem with another windows function and then posting about that function in a loop so as to solve my original problem through subversion of this community, I'd just be upfront about it.

    EDIT:
    Quote Originally Posted by cboard guidelines
    6. Messages relating to cracking, (erroneously called "hacking" by many), copyright violations, or other illegal activities will be deleted. This includes all messages reguarding to keyloggers.
    If that includes studying cracking as well as attempting it, then I apologize for violating the rules. Go ahead and delete this post, sorry to have wasted your time.
    Last edited by RaccoonKing; 07-17-2006 at 06:34 PM.

  6. #6
    pwns nooblars
    Join Date
    Oct 2005
    Location
    Portland, Or
    Posts
    1,094
    I have studied several types of breaking and entering security wise... SQL injection being the one I have worked on the most... but I wrote the page I was trying to crack, on an instance of the database that I had put data into myself. You could easily simulate brute force methods with assigning a variable a value then use a fucntion to try and guess that variable. There is no legitimate way to justify attempting to break into windows, what ever you end up writing could easilly be used maliciously and that is why I believe your post violates what cboard is about.

  7. #7
    (?<!re)tired Mario F.'s Avatar
    Join Date
    May 2006
    Location
    Ireland
    Posts
    8,446
    If you want to test break force attacks, std::cin a password and then std::cout the brute force attack. Just don't give me that sweet talk you are trying to learn.

    Anyways, the quote you provided was pretty obvious. It says "messages relating to". That includes trying to understand how it works. Try the Newsgroups. You'll get better served. Just don't tell them you are trying to learn brute force attacks. The answers will... not be gentle and you will be laughed at.
    Last edited by Mario F.; 07-17-2006 at 07:29 PM.
    Originally Posted by brewbuck:
    Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.

  8. #8
    Registered User
    Join Date
    Jul 2005
    Posts
    12
    If you say so. It just seems like a drastic and emotionally-driven overreaction that obfuscates programmers from learning objectively about how their code is exploited.

    Anyway, this type of message won't be repeated. Again, you have my apologies for the violation.

  9. #9
    the hat of redundancy hat nvoigt's Avatar
    Join Date
    Aug 2001
    Location
    Hannover, Germany
    Posts
    3,130
    Closed
    hth
    -nv

    She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."

    When in doubt, read the FAQ.
    Then ask a smart question.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Help with insert/delete binary search tree
    By Nazgulled in forum C Programming
    Replies: 39
    Last Post: 03-25-2009, 04:24 PM
  2. Problems with shared memory shmdt() shmctl()
    By Jcarroll in forum C Programming
    Replies: 1
    Last Post: 03-17-2009, 10:48 PM
  3. Shared Memory - shmget questions
    By hendler in forum C Programming
    Replies: 1
    Last Post: 11-29-2005, 02:15 AM
  4. Memory allocation and deallocation
    By Micko in forum C++ Programming
    Replies: 3
    Last Post: 08-19-2005, 06:45 PM
  5. Pointer's
    By xlordt in forum C Programming
    Replies: 13
    Last Post: 10-14-2003, 02:15 PM