Sponsored Content
Full Discussion: Slackware: libxml2
Special Forums Cybersecurity Security Advisories (RSS) Slackware: libxml2 Post 302260343 by Linux Bot on Thursday 20th of November 2008 09:10:03 AM
Old 11-20-2008
Slackware: libxml2

LinuxSecurity.com: New libxml2 packages are available for Slackware 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, and -current to fix security issues including a denial or service or the possible execution of arbitrary code if untrusted XML is processed. More details about the issues may be found in the Common Vulnerabilities and Exposures (CVE) database:

More...
 

5 More Discussions You Might Find Interesting

1. Programming

libxml2

hi all is libxml2 version dependent? can you please explain about it. thank you in advance (2 Replies)
Discussion started by: munna_dude
2 Replies

2. Ubuntu

libxml2-dev

Hi again, I use Ubuntu 8.10. I could not install xml-config. Although libxml2-dev is installed, ./configure cannot find xml-config. Help me out please... apprentice (7 Replies)
Discussion started by: apprentice
7 Replies

3. Programming

libxml2 documentation

i need to read/write a xml file in c i found libxml2, but the documentation is awfull, im using google but i get most of vb, or c# results can anyone point me to a introduction tutorial? actually, any kind of documentation would be ok (just not the oficial The XML C parser and toolkit... (2 Replies)
Discussion started by: broli
2 Replies

4. UNIX for Dummies Questions & Answers

Which version of libxml2?

What method do you use to find out what version of libxml2 one uses on Linux? I have tried the following: $ libxml2 -v libxml2: command not found $ libxml2 --version libxml2: command not found $ which libxml2 $ There is however a /usr/lib/libxml2.so.2.7.5. (1 Reply)
Discussion started by: figaro
1 Replies

5. Programming

How to get the number of bytes parsed in libxml2

Hi, I am using the libxml2 sax parser to parse a in memory xml string along with validating it against a schema. I am using the following code: xmlSAXHandlerPtr sax_ = new xmlSAXHandler(); sax_->initialized = XML_SAX2_MAGIC; sax_->startElementNs =... (0 Replies)
Discussion started by: Sam Krishna
0 Replies
ND(1)							      General Commands Manual							     ND(1)

NAME
nd - Tiny little command line WebDAV interface SYNOPSIS
nd [options] url DESCRIPTION
nd provides a simple command line interface to the RFC 2518 (WebDAV) server. If no option is specified, HTTP GET command is issued and writes response data to the standard output. The options are as follows: -c dest_url COPY url to the dest_url. Use lock token if -t is specified. -f Force override the content even when the MOVE or COPY target already exits. -v View property information of url by PROPFIND. With -g option, only the specified property is displayed. -p file PUT file content to the url. Use lock token if -t is specified. -g name Specify the property name for -v option. -e name=value Edit the property with name to value using PROPPATCH . -N namespace-url Specify the property namespace URL for -e or -g option. -P file POST file content to the url. -T is used for the Content-Type. -T content_type Use content_type as a Content-Type field value of the POST request. Default is `application/x-www-form-urlencoded'. -d DELETE url. Use lock token if -t is specified. -l LOCK url. Use -o as owner, -s as scope, -i as timeout. -o owner Specify lock owner. Default is USER environment variable. -s scope Specify lock scope (`exclusive' or `shared'). Default is `exclusive'. -i timeout Specify lock timeout interval. Default is `Infinite'. -u UNLOCK url. -t option is required. -t token Specify the lock token. -r Set command execution `Depth' as `Infinity'. -a realm Specify authentication realm. -A realm Specify proxy authentication realm. -k MKCOL url -m dest_url MOVE url to the dest_url. Use lock token if -t is specified. -S Print output using s-expression. ENVIRONMENT VARIABLES
http_proxy, HTTP_PROXY Specify HTTP proxy. USER When manipulating a lock without an explicit owner option, the value of USER is used to set the owner of the file lock. BUGS
A maintainer of the Debian package has implemented Digest authentication on top of the original software. However, the upstream source uses the nanoHTTP code from libxml2 to implement the HTTP transport. Due to properties inherent in that code for detecting and following redi- rected target sites, there is no way to pull out the new address in order to insert it into the hashes necessary for the Digest method. Nd will therefore incorrectly answer with 'Bad request' to any method call aimed at such sites. Using the correct logical name for the target will, however, produce a correct response from Nd. AUTHORS
Yuuichi Teranishi (teranisi@gohome.org). SEE ALSO
libxml(4). February 25, 2002 ND(1)
All times are GMT -4. The time now is 06:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy