Re: svn update failures

[Patrik Karlsson <patrik () cqure net>]

On Tue, May 15, 2012 at 11:47 PM, Forrest Aldrich <forrie () gmail com> wrote:

> I'm still having the same trouble.
>
> Okay, so if I'm going to have to type in a username for each update tree,
> which anonymous one should I use?
>
> Forrest
>
>
>
> # svn update
> U    nmap-service-probes
> D    scripts/asn-to-prefix.nse
> U    scripts/rexec-brute.nse
> U    scripts/http-domino-enum-**passwords.nse
> U    scripts/firewalk.nse
> U    scripts/dns-cache-snoop.nse
> U    scripts/acarsd-info.nse
> U    scripts/lltd-discovery.nse
> U    scripts/xmpp-info.nse
> U    scripts/smtp-vuln-cve2010-**4344.nse
> U    scripts/asn-query.nse
> U    scripts/ganglia-info.nse
> U    scripts/targets-sniffer.nse
> U    scripts/ssl-enum-ciphers.nse
> U    scripts/whois.nse
> U    scripts/http-vuln-cve2010-**2861.nse
> U    scripts/reverse-index.nse
> D    scripts/hostmap.nse
> U    scripts/smtp-open-relay.nse
> U    scripts/drda-info.nse
> U    scripts/smtp-vuln-cve2011-**1764.nse
> U    scripts/http-qnap-nas-info.nse
> U    scripts/svn-brute.nse
> U    scripts/http-backup-finder.nse
> U    scripts/http-php-version.nse
> U    scripts/smb-security-mode.nse
> U    scripts/http-barracuda-dir-**traversal.nse
> U    scripts/pop3-brute.nse
> U    scripts/script.db
> U    scripts/ftp-brute.nse
> U    scripts/http-affiliate-id.nse
> A    scripts/ajp-request.nse
> A    scripts/rdp-vuln-ms12-020.nse
>
> Authentication realm: <https://svn.nmap.org:443> svn.nmap.org
> Password for 'root':
>
> Authentication realm: <https://svn.nmap.org:443> svn.nmap.org
> Username: guest
> Password for 'guest':
> svn: Server sent unexpected return value (403 Forbidden) in response to
> OPTIONS request for 'https://svn.nmap.org&apos;
>
>
>
> ______________________________**_________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/**mailman/listinfo/nmap-dev<http://cgi.insecure.org/mailman/listinfo/nmap-dev>
> Archived at http://seclists.org/nmap-dev/

Is there any particular reason for having the server root directory
password protected? If that's what's causing the error, which seems likely
given the last error message, simply having it return a 404 or 200 could
perhaps solve the problem.

//Patrik

-- 
Patrik Karlsson
http://www.cqure.net
http://twitter.com/nevdull77
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/