[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP279ADC1DEEEB07747DE549EFD200@phx.gbl>
Date: Fri, 4 Jan 2013 18:48:15 +0100
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: fmt_main conventions
On 01/04/2013 06:32 PM, Lukas Odzioba wrote:
> I changed names of fmt_main structs listed below, to be consistent
> with naming convention we use most often:
> -name starts with "fmt_" prefix, or "fmt_opencl", "fmt_cuda" for gpu formats.
>
> Affected names:
> sha1_fmt_ng -> fmt_sha1_ng
> fmt_ocl_krb5pa_sha1 -> fmt_opencl_krb5a_sha1
> rar_fmt -> fmt_rar
> zip_fmt -> fmt_zip
> mozilla_fmt ->fmt_mozilla
Good idea.
While you are at it, can you change these as well:
KeePass_fmt
agile_keychain_fmt
chap_fmt
dmg_fmt
episerver_fmt
ike_fmt
keychain_fmt
keyring_fmt
lastpass_fmt
mongodb_fmt
mysqlna_fmt
nk_fmt
o5logon_fmt
odf_fmt
office_fmt
oldoffice_fmt
postgre_fmt
pst_fmt
pwsafe_fmt
racf_fmt
radmin_fmt
sip_fmt
sshng_fmt
strip_fmt
sxc_fmt
vnc_fmt
wbb3_fmt
Frank
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
