Skip to content

Commit 834fad4

Browse files
inflexinflex
committed
Initial upload of all files to git
1 parent a1d4cfb commit 834fad4

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

66 files changed

+23507
-18
lines changed

‎CHANGELOG

Lines changed: 1762 additions & 0 deletions
Large diffs are not rendered by default.

‎CONTRIBUTORS

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
Original Author : Paul L Daniels
2+
3+
---------------------------
4+
Author : Farit
5+
Date : 14/01/2004
6+
Contrib: Supplied various mailpacks with exploits/viruses/worms and
7+
alternative 'header' prefixing.
8+
9+
---------------------------
10+
Change : Correction of various spurilous messages appearing even when
11+
verbosity is not active
12+
Date : 26/01/2003
13+
Author : Chris Hine
14+
15+
---------------------------
16+
Change : Change char * to unsigned char * in strlower() function to deal with
17+
non-ASCII characters ( ie, French, Chinese )
18+
Date : 09/11/2002
19+
Author : Emmanuel Collignon
20+
21+
22+
23+
---------------------------
24+
Change : Patch to deal with spaces inbetween name=, filename= type
25+
MIME headers. Submitted by Phil Brutsche
26+
Date : 06/11/2002
27+
28+
29+
---------------------------
30+
Change : Updates to FFGET routines. Improve handling of one-off issues and
31+
buffer boundary conditions
32+
Author : Joseph Gooch
33+
Email :
34+
Date : 27/02/2002
35+
36+
Notification : Version number update (I hate it when I forget that)
37+
Notifier : wes schreiner
38+
Date : 21/02/2002
39+
40+
---------------------------
41+
Change : TNEF decoding improvements - Quoted Printable decoding fixes
42+
Author : Chea Chee Keong
43+
Email : [email protected]
44+
Date : 20/02/2002
45+
46+
---------------------------
47+
Change : CRCR logic clarification
48+
Author : Joseph Gooch
49+
Date : 18/02/2002
50+
51+
---------------------------
52+
Change : TNEF decoding improvements
53+
Author : Chea Chee Keong
54+
Email : [email protected]
55+
Date : 01/01/2002
56+
57+
---------------------------
58+
Change : add ability to read mimepack from STDIN
59+
Author : Matthew McNaughton <[email protected]>
60+
Date : 24/11/2000
61+
62+
---------------------------
63+
Fixes:
64+
Change : Correction for handling varying line-length BASE64 encoded files
65+
Author : Trent, Michael (Xerox USA) and John Armstrong (EFI.com)
66+
Date : 05/11/2001
67+
68+
---------------------------
69+
Change : Support for SGI systems (fixes lockup)
70+
Author : Don Lafontaine <[email protected]>
71+
Date : 27/09/2001
72+
73+
---------------------------
74+
Change : Correct problem where a filename will contain multiple consecutive /'s
75+
Author : James Cownie
76+
Date : 03/02/2001
77+
78+
---------------------------
79+
Change : Replaced the tmpnam() call for temporary filename with MIME_tmpnam()
80+
Author : Dave DeMaagd & Paul L Daniels
81+
Date : 29/01/2001
82+
83+
---------------------------
84+
Change : added patch to detected boundaries without surrounding quotations
85+
Author : Rolf
86+
Date : 12/01/2001
87+
88+
89+
---------------------------
90+
Support:
91+
Date : 07/01/2000
92+
Person: Hans Harder
93+
What: Supplied me with a mailpack which couldn't be correctly decoded by ripMIME due to it not having a trailing CR/LF after the base64 encoded portion of the attachment.
94+
95+
---------------------------
96+
Date : 29/01/2001
97+
Person : Sven Rassmaan
98+
What: Supplied me with a mailpack/spool which I could test the multiple-email-spool-extract facility (also happened to be the requestor or such)

‎INSTALL

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
INSTALL---------------------------------------------------------------
2+
3+
Very simple (as root)...
4+
5+
make
6+
make install
7+
8+
[ Make install will install the ripmime binary to /usr/local/bin,
9+
there are no other support files required. ]
10+
11+
To use ripMIME...
12+
13+
If you have an MIME encoded archive (say from sendmail's output)
14+
called recvmail001.mime and you wish to unpack it to a directory
15+
(which already exists) called "/var/tmp/unpack", then use ripMIME
16+
as follows...
17+
18+
ripmime -i recvmail001.mime -d /var/tmp/unpack
19+
20+
It's truly that simple.
21+
22+
--- If you want more PERFORMANCE out of ripMIME (most people will), you can
23+
select some compile flags in the Makefile which suit your CPU better,
24+
ie, for recent Pentiums/Celerons, you can use
25+
26+
-Wall -O3 -march=i686
27+
28+
29+
----------------------------------------------------------------------
30+
31+
Enjoy.

‎LICENSE

Lines changed: 28 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,33 @@
1-
Copyright (c) 2016, Inflex
1+
Copyright (c) 2003, PLD
22
All rights reserved.
33

4-
Redistribution and use in source and binary forms, with or without
5-
modification, are permitted provided that the following conditions are met:
4+
Redistribution and use in source and binary forms, with or
5+
without modification, are permitted provided that the
6+
following conditions are met:
67

7-
* Redistributions of source code must retain the above copyright notice, this
8-
list of conditions and the following disclaimer.
8+
* Redistributions of source code must retain the above
9+
copyright notice, this list of conditions and the following
10+
disclaimer.
911

10-
* Redistributions in binary form must reproduce the above copyright notice,
11-
this list of conditions and the following disclaimer in the documentation
12-
and/or other materials provided with the distribution.
12+
* Redistributions in binary form must reproduce the above
13+
copyright notice, this list of conditions and the following
14+
disclaimer in the documentation and/or other materials provided
15+
with the distribution.
16+
17+
* Neither the name of the PLD nor the names of its contributors
18+
may be used to endorse or promote products derived from this software
19+
without specific prior written permission.
20+
21+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
22+
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
23+
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
24+
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
25+
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
26+
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
27+
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
28+
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
29+
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30+
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
31+
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
32+
POSSIBILITY OF SUCH DAMAGE.
1333

14-
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
15-
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16-
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
17-
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
18-
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19-
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
20-
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
21-
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
22-
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
23-
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

0 commit comments

Comments
 (0)