[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Almost repetitive repository corruption

From: Igor Varfolomeev <i3v_at_mail.ru>
Date: Mon, 30 Dec 2013 22:06:54 +0000 (UTC)

Thorsten Schöning <tschoening <at> am-soft.de> writes:

>
> Guten Tag Igor Varfolomeev,
> am Sonntag, 29. Dezember 2013 um 23:00 schrieben Sie:
>
> > Antivirus: Kaspersky Endpoint Security 10
> [...]
> > 1. What was that? Any ideas? May it happen again?
>
> I would have a look on the (signature) updates for your Kaspersky, if
> some updates arrived just after your bug disappeared.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>

To my shame, this is SLIGHTLY possible. Kaspersky downloads something
every 2 hours.... So, signatures did had changed during these
experiments. Though, as I've already said on tortoise svn mailing list,

(
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3070904
)

that I doubt it was intentional blocking since:

1) There should be a popup

2) There should be corresponding records in "Reports"

3) There's an option to "Disinfect" (even to "auto-disinfect"), but
   I've disabled it, it never was allowed...

4) I've made an experiment: committed a "infected" file
   (see http://www.rexswain.com/eicar.html )
   to a repository and THEN
   allowed KEPS to scan it - no corruption happened.

5) Another experiment: when I try to commit same file with
   KEPS on - commit fails with "Can't open file" error in this case.

Of course, these two experiment proof nothing, but still, I doubt
that was intentional Kaspersky's behavior.

There might be some king of interference between svn and Kaspersky,
but, most possibly, it won't depend on signatures. Moreover,
in case there would be such interference, I think, I won't be
the first to ran into it....
Received on 2013-12-30 23:07:51 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.