how to replicate svn-lock on mirrored repository

[Senthilvelu]

I  have a mirrored repository which is generated from a source repository.

it is getting update regularly. when a user checks out with lock on source 
repo, i want this to be update on the mirror repo, which is not happening 
using svnsync.

is there anyway i can update the lock as well on the mirror repo

thanks senthil

SVN exception when trying to commit

[Vincent, Tom]

I'm having the following error when I try to commit:

---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
'D:\Development\SVN\Releases\TortoiseSVN-1.8.8\ext\subversion\subversion\libsvn_wc\wc_db.c'
line 3600: assertion failed (db_kind == svn_node_file || db_kind ==
svn_node_dir)
---
OK
---

Any assistance you can provide would be great - I'm not subscribed to the list 
so If you could cc me on any responses I'd appreciate it.

Thanks,

Tom

--
This e-mail and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error please notify the sender 
immediately and delete this e-mail from your system.
Please note that any views or opinions presented in this e-mail are solely 
those of the author and do not necessarily represent those
of Ricardo (save for reports and other documentation formally approved and 
signed for release to the intended recipient). Only Directors
are authorised to enter into legally binding obligations on behalf of Ricardo. 
Ricardo may monitor outgoing and incoming e-mails and
other telecommunications systems. By replying to this e-mail you give consent 
to such monitoring. The recipient should check e-mail and
any attachments for the presence of viruses. Ricardo accepts no liability for 
any damage caused by any virus transmitted by this e-mail.
"Ricardo" means Ricardo plc and its subsidiary companies.
Ricardo plc is a public limited company registered in England with registered 
number 00222915.
The registered office of Ricardo plc is Shoreham Technical Centre, Shoreham-by 
Sea, West Sussex, BN43 5FG.
--

Different behaviour of storing plaintext passwords under Unix - svn log differes from svn co/up

[Schulz, Gunther]

Hello,

I detected an unexpected behaviour of the subversion client (Debian 7.7, svn 
version 1.6.12 (r955767)):

The configuration settings of store-plaintext-passwords (yes/ask/no) are only 
validated if I execute svn commands like checkout or update, but not for a 
simple 'svn log' command:

-   the password file in auth/svn.simple were not generated

-   strangely I was asked if I want to store the hostkey certificate which 
worked seemlessly

-   when using a 'svn update' or 'svn checkout' the expected behaviour was 
seen (prompt for saving or save automatically)

Usually this is not detected as one of the first calls are update or checkout 
commands, but I used here some scripting using 'svn log' and was wondering why 
my password was never updated, no matter where I changed the 
save-plaintext-passwords settings (/etc/subversion/servers or 
~/.subversion/servers, global section or specific local server sections).

I assume this is a bug or at least a strange feature. Normally I would expect 
that the same authentication procedure is used for all the remote svn commands 
which require authentication against the server.

Please let me know if you need some traces or configuration settings...

BTW: Subversion server was running on a Windows server machine, access via 
WebDAV / https

Best regards,

Gunther

--

-

Carl Zeiss SMT GmbH
Carl Zeiss Gruppe
Lithography Optics Division / Technology Mechatronics
Department LIT-TES

G u n t h e r  S c h u l z

Phone: +49 73 64 20-9672
mailto:   gunther.sch...@zeiss.com | 
http://www.zeiss.com/smt


Carl Zeiss SMT GmbH
Rudolf-Eber-Straße 2, 73447 Oberkochen
Geschäftsführung: Dr. Hermann Gerlinger (Vorsitzender), Dr. Andreas Dorsel, 
Axel Jaeger
Sitz der Gesellschaft: 73447 Oberkochen, Deutschland
Amtsgericht Ulm, HRB 725667, USt-IdNr: DE 8
-

Re: Different behaviour of storing plaintext passwords under Unix - svn log differes from svn co/up

[Bert Huijben]

Does your server support anonymous read only connections?


If it allows those, it is completely expected that it doesn't use a password 
for authorizing things like log… and therefore never updates/stores passwords 
in that case.


Bert





From: Schulz, Gunther
Sent: ‎Friday‎, ‎November‎ ‎21‎, ‎2014 ‎4‎:‎05‎ ‎PM
To: users@subversion.apache.org






Hello,

 

I detected an unexpected behaviour of the subversion client (Debian 7.7, svn 
version 1.6.12 (r955767)):

 

The configuration settings of store-plaintext-passwords (yes/ask/no) are only 
validated if I execute svn commands like checkout or update, but not for a 
simple ‘svn log’ command:

-   the password file in auth/svn.simple were not generated

-   strangely I was asked if I want to store the hostkey certificate which 
worked seemlessly

-   when using a ‘svn update’ or ‘svn checkout’ the expected behaviour was 
seen (prompt for saving or save automatically)

 

Usually this is not detected as one of the first calls are update or checkout 
commands, but I used here some scripting using ‘svn log’ and was wondering why 
my password was never updated, no matter where I changed the 
save-plaintext-passwords settings (/etc/subversion/servers or 
~/.subversion/servers, global section or specific local server sections).

 

I assume this is a bug or at least a strange feature. Normally I would expect 
that the same authentication procedure is used for all the remote svn commands 
which require authentication against the server.

 

Please let me know if you need some traces or configuration settings…

 

BTW: Subversion server was running on a Windows server machine, access via 
WebDAV / https

 

Best regards,

 

Gunther

 

--

-

Carl Zeiss SMT GmbH
Carl Zeiss Gruppe
Lithography Optics Division / Technology Mechatronics
Department LIT-TES

G u n t h e r  S c h u l z

Phone: +49 73 64 20-9672
mailto:   gunther.sch...@zeiss.com | http://www.zeiss.com/smt


Carl Zeiss SMT GmbH
Rudolf-Eber-Straße 2, 73447 Oberkochen
Geschäftsführung: Dr. Hermann Gerlinger (Vorsitzender), Dr. Andreas Dorsel, 
Axel Jaeger
Sitz der Gesellschaft: 73447 Oberkochen, Deutschland
Amtsgericht Ulm, HRB 725667, USt-IdNr: DE 8
-

Re: SVN exception when trying to commit

[Ryan Schmidt]

On Nov 21, 2014, at 6:29 AM, Vincent, Tom wrote:

> I’m having the following error when I try to commit:
>  
> ---
> Subversion Exception!
> ---

We'll probably need more information from you. Obviously if commit were broken 
in all cases, everyone would be complaining about it. Does this problem happen 
only with one working copy? Does it happen every time or intermittently? Does 
checking out a new working copy of that repository help?

Setting up a mirror - should I use the same repository UUID, or different?

[Eric Johnson]

I'm setting up a Subversion mirror, and trying to figure out whether I
should have the mirror repositories have the same UUID or a different UUID
on the mirror.

Currently, I'm using the same UUID, so that should someone wish to do an
svn switch relocate between the two servers, they can do that.

Anyone with experience that suggests that that is a bad idea?

Eric.

Re: Setting up a mirror - should I use the same repository UUID, or different?

[Ryan Schmidt]

On Nov 21, 2014, at 7:30 PM, Eric Johnson wrote:
> 
> I'm setting up a Subversion mirror, and trying to figure out whether I should 
> have the mirror repositories have the same UUID or a different UUID on the 
> mirror.
> 
> Currently, I'm using the same UUID, so that should someone wish to do an svn 
> switch relocate between the two servers, they can do that.
> 
> Anyone with experience that suggests that that is a bad idea?

Right, using the same UUID would be necessary to allow users to relocate 
between the mirror(s) and the master. This is suggested here:

https://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt

The mirror might be some commits behind the master depending on how fast syncs 
happen, but that shouldn't be a problem since the mirrors are read-only and 
users can only commit to the master.

Re: Different behaviour of storing plaintext passwords under Unix - svn log differes from svn co/up

[Branko Čibej]

On 21.11.2014 16:05, Schulz, Gunther wrote:
>
> -   strangely I was asked if I want to store the hostkey
> certificate which worked seemlessly
>

The server certificate does not contain any passwords or private keys,
and anyone can download it simply by creating an SSL connection to your
server (with 'openssl s_client', for example). So it's not considered
insecure to store that on disk, unencrypted.

There is a possible attack vector through that: Since Subversion was
told to trust the stored certificate, one can imagine a situation where
an attacker (a) subverts IP routing and/or DNS to redirect your
connections to their own server, with a different certificate; (b)
breaks in to your, and (c) every other, client machine to change their
stored server certs. However, at least (c) unlikely.

OTOH, since "unlikely" is not the same as "can't happen", we should
perhaps consider not storing the server cert, too, if plaintext password
storage is disabled.

-- Brane

P.S.: Compare the above scenario with the far more simple and likely one
where the attacker breaks into your server and steals it wholesale,
including the server's private key.