Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
html2text /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
CREDITS
953
B
-rw-r--r--
KNOWN_BUGS
1.49
KB
-rw-r--r--
NEWS.Debian.gz
464
B
-rw-r--r--
README.Debian
2.06
KB
-rw-r--r--
README.gz
3.74
KB
-rw-r--r--
TODO
2.59
KB
-rw-r--r--
ascii.substitutes
3.76
KB
-rw-r--r--
changelog.Debian.gz
1.69
KB
-rw-r--r--
copyright
4.21
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : KNOWN_BUGS
## KNOWN_BUGS - Problems with html2text Sat Jul 5 12:40:24 CEST 2003 ## =========================================================================== # ( 0 )======================================================================= # Feature requests # ( 0.1 )--------------------------------------------------------------------- # Make HTTP implementation optional? A corresponding compile-time option would enhance portability (no socket() needed). Moreover, html2text's HTTP implementation is rather rudimentary, so it maybe could be eliminated completely. But I don't know how many users prefer to have html2text to fetch the files by itself instead of using it within a pipe... This however would lead to a complete re-write of the configure-script, because we don't have any compile-time options yet. # ( 1 )======================================================================= # Bugs of minor severity # # The package fails to perform correctly on some conditions, or in some # systems, or fails to comply current policy documents. # ( 1.1 )--------------------------------------------------------------------- # When parsing much nested TABLEs, html2text will run out of control. This problem occurs on very complex tables with more than about 25 nested TABLE elements, because the runtime increases exponentially with each nested table. Sorry, no fix for this within sight. # ============================================================================ Martin Bayer <mbayer@zedat.fu-berlin.de>
Close