Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update src/dynamic_utils.c #1

Merged
merged 1 commit into from
Dec 17, 2011
Merged

Update src/dynamic_utils.c #1

merged 1 commit into from
Dec 17, 2011

Conversation

jfoug
Copy link
Collaborator

@jfoug jfoug commented Dec 17, 2011

Trying stuff out. This is the correct changes. Just how the hell is this supposed to work. Seems very inefficient if there is no way to run diffs across already written source.

Jim.

@magnumripper magnumripper merged this pull request into openwall:magnum-jumbo Dec 17, 2011
@magnumripper
Copy link
Member

I just pulled this via the web gui. Seems easy enough. Next time I'll try configuring your branch as a remote (in my local tree) and pull directly from command line.

There are all sorts of ways you can diff between files, branches, versions or whatever when using the local tools. I wont use this web gui much.

@jfoug
Copy link
Collaborator Author

jfoug commented Dec 17, 2011

So, what would you recommend for my usage of this? From what I saw, it looked VERY limited, and if that is all there is, I will not be using it. My method simply has 3 'working' directories on my drive. I have my 'real' work in progress dir. I then have 2 dirs that I keep up to date with patches (I also keep my WIP dir up to date with patches). Then when I want to submit a patch, I use a GUI diff program to move just the changes I want from my WIP dir, to the 2nd dir. I then build the patch from doffing between the 2nd and 3rd dir. I then patch the 3rd dir to make sure the patch is happy.

I then build on dir 2, and do a test.

Utilizing that procedure, I never have a bad patch, and also get things tested well.

I simply have to find the usage procedures for this git, and make sure it works 'well' enough with multiple people whacking on the DB.

I have used CSV before, and it's not bad. You can put a java client on your local, and do some pretty impressive things with your local source tree, against the remote repository. Hopefully, git can be done in a similar manner, I just have to learn the ins and outs of its usage, and get properly setup with r+w access.

Whats up with the strange return address (I also cc'd what I know to be a good addy).

Jim.

-----Original Message-----
From: magnum [mailto:reply+i-2590022-
b7de1affea831b72728ac2ab4d645ae69fb74bdc-1270024@reply.github.com]
Sent: Saturday, December 17, 2011 4:22 PM
To: jfoug
Subject: Re: [magnum-jumbo] Update src/dynamic_utils.c (#1)

I just pulled this via the web gui. Seems easy enough. Next time I'll
try configuring your branch as a remote (in my local tree) and pull
directly from command line.

There are all sorts of ways you can diff between files, branches,
versions or whatever when using the local tools. I wont use this web gui
much.


Reply to this email directly or view it on GitHub:
https://github.com/magnumripper/magnum-jumbo/pull/1#issuecomment-3191848

@jfoug
Copy link
Collaborator Author

jfoug commented Apr 13, 2012

It adds multiple charsets to the 'double' extern 'class'. I 'may' make a
change beyond this, to add a reverse (makes a palindrome). But for now, this
is a good change.

Jim.

sayan1an added a commit that referenced this pull request Jul 28, 2013
magnumripper added a commit that referenced this pull request Jul 29, 2013
* bleeding-jumbo:
  loader: added sequential id for salts
  add more test vectors in ecryptfs format
  add ecryptfs2john utility
  mscash-opencl: optimization patch #3
  mscash-opencl: optimization patch #2
  mscash-opencl: optimization patch #1
  format for cracking eCryptfs
  mscash-opencl: optimization patch #0
magnumripper added a commit that referenced this pull request Aug 10, 2013
sayan1an added a commit that referenced this pull request Aug 10, 2013
magnumripper added a commit that referenced this pull request Aug 10, 2013
* bleeding-jumbo: (21 commits)
  Fix after reverts.
  Mask mode for GPU
  Revert "Raw-MD5-opencl: compare on gpu"
  Revert "Raw-MD5-opencl: fixed memory cleanup"
  Revert "Update opencl_rawmd5_fmt.c"
  Revert "Raw-MD5-opencl: status check bug fix"
  Revert "raw-md5-opencl bugfix: You can't release buffers that are not allocated."
  Revert "nt-opencl: cmp on gpu"
  Revert "nt-opencl: use opencl_init instead of opencl_init_opt"
  Revert "raw-md4-opencl:cmp on gpu"
  Revert "raw-sha1-opencl: cmp on gpu"
  Revert "New format added, mscash-opencl: ported directly from mscash-cuda."
  Revert "mscash-opencl: optimization patch #0"
  Revert "mscash-opencl: optimization patch #1"
  Revert "mscash-opencl: optimization patch #2"
  Revert "mscash-opencl: optimization patch #3"
  Revert "Various minor fixes for Sayantan's OpenCL versus OS X."
  Revert "mscash-opencl: compare on gpu"
  Revert "nt-opencl: fixed bug causing inefficient keys transfer."
  Revert "added mask mode interface"
  ...

Conflicts:
	src/opencl_nt_fmt.c
	src/opencl_rawmd4_fmt.c
	src/opencl_rawsha1_fmt.c
frank-dittrich added a commit to frank-dittrich/john that referenced this pull request Jun 11, 2014
Compiling: DES benchmark (code version openwall#1)
make[1]: Entering directory `/home/fd/git/JtR/src'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.

Instead of adding '+' to the "parent" make rule I passed -j1 to ./best.sh
sayan1an added a commit that referenced this pull request Dec 18, 2014
kholia pushed a commit that referenced this pull request Feb 24, 2015
@jfoug jfoug deleted the patch-1 branch June 16, 2015 21:34
@ghost ghost mentioned this pull request Aug 28, 2016
magnumripper pushed a commit that referenced this pull request Sep 12, 2016
libbz2-dev needed for bzlib.h successfull check for "BZ2 (gpg2john extra decompression logic) ... yes"
@no1deer no1deer mentioned this pull request Aug 18, 2018
@davidwarr davidwarr mentioned this pull request Dec 1, 2019
@MESWEB MESWEB mentioned this pull request Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants