sorry for the noice
sorry (again) about the noise. That's the last one, promised 8-)
I looked it up and it doesn't give me any leads:
#define ECONNABORTED103 /* Software caused connection abort */
Any other ideas?
On 11/05/2015 10:29 PM, Daniel Shahaf wrote:
Timothy Astle wrote on Mon, May 11, 2015 at 08:16:25 -0300:
Error writing base64 data. Software caused
Hi,
I would like to set up SVN to store confidential documents.
I have secured the pipe communication with HTTPS/SSL. To avoid
unauthorized users (even with root access) accessing documents from within
the server, I would like to protect the SVN linux folder/files with
encryption.
Are there any
Hi all,
can someone please check if this realy is a regression, or if it is
just me doing something wrong.
I have a problem with "svn -v status" showing an unexpected result for
file externals.
This seems to be a regression that happended with svn 1.8.12/13
I've tried this with the binaries bu
> On May 12, 2015, at 5:30 AM, D Ste wrote:
>
> Hi,
>
> I would like to set up SVN to store confidential documents.
> I have secured the pipe communication with HTTPS/SSL. To avoid unauthorized
> users (even with root access) accessing documents from within the server, I
> would like to pr
> On May 12, 2015, at 8:45 AM, jbl...@icloud.com wrote:
>
>
>> On May 12, 2015, at 5:30 AM, D Ste wrote:
>>
>> Hi,
>>
>> I would like to set up SVN to store confidential documents.
>> I have secured the pipe communication with HTTPS/SSL. To avoid unauthorized
>> users (even with root acces
We recently upgraded our Subversion server from 1.6 to 1.8 and since
then some of our users
our reporting problems checking out certain folders using a 1.8
client. The issues occur whether using TortoiseSVN 1.8.x or any 1.8
CLI client on Windows/Cygwin/Linux.
We have verified that these operatio
If a user has root access to your host then nothing is going to be completely
secure on that host.
The encryption key could potentially be read from memory or the resulting
decrypted repository contents from memory.
If you don't trust your root users then you've got bigger problems regarding
t
Hello,
On 12/05/15 18:27, Clay Porter wrote:
> svn: E175002: GET request failed: 400 Bad request
> There is no corresponding error in the Apache HTTP logs.
>
> svn: E200014: Checksum mismatch for
>expected: 4b4ef9e3432aa84aed190457b68c01ad
> actual: 863b9f52f352a5cb20298ef0eecb9e97
>
On Tue, May 12, 2015 at 8:30 AM, D Ste wrote:
> Hi,
>
> I would like to set up SVN to store confidential documents.
> I have secured the pipe communication with HTTPS/SSL. To avoid unauthorized
> users (even with root access) accessing documents from within the server, I
> would like to protect t
11 matches
Mail list logo