Re: [Burp-users] Burp-users Digest, Vol 2, Issue 2

[Israel B. <bra...@gm...>]

On 03/16/2011 01:44 PM, bur...@li... wrote:
>
> Message: 7
> Date: Wed, 16 Mar 2011 11:44:28 +0000
> From: Graham Keeling <ke...@sp...>
> Subject: [Burp-users] authorization problems
> To: bur...@li...
> Message-ID: <201...@in...>
> Content-Type: text/plain; charset=us-ascii
>
> Israel Bravo wrote:
>> Server - burp-1.1.14 - Linux CentOS
>> Client - burp-1.1.14 - Windows 7 32 bit and 64 bit (checked on two computers)
>> After starting "burp -a b"  (immediately after installation) I get error messages (see attached snapshot).
>> I don't understand why the message is "expected c:ok, got e:unable to authorise" - disk E is CD-ROM !
> a) You need to use forward slashes in your include path ('/' instead of '\'),
> or your backups will go funny once you start adding more than one
> include/exclude.
            Done.
> b) When burp says "expected c:ok, got e:unable to authorise", it means that
> it was expecting the server to say 'c:ok' (command ok) to the authorisation
> request. But it actually got 'e:unable to authorise'. This means 'error -
> unable to authorise', not something to do with your E drive.
>
> You need to check that there is an entry for the client in
> the clientconfdir on the server that matches the cname field in the client
> burp.conf file, and that the password fields match.
>
> So, in your client burp.conf file, there will be two lines like this:
> cname = someclientname
> password = somepassword
>
> On the server, you will need to create a file named like this (assuming that
> you have not changed the clientconfdir path in the server conf file):
> /etc/burp/clientconfdir/someclientname
>
> Inside that file on the server, you will need at least these options (assuming
> that you have not created your own ssl certificates):
> password = abcdefgh
> ssl_peer_cn = grkeclient

        The problem was that the word "grkeclient" had a trailing space.
        After removing this space the backup started successfully