“The phrase “a real possibility” is to be contrasted with the extravagant fears which seem to afflict all plaintiffs who have complaints of breach of confidence, breach of copyright or passing off. Where the production and delivery up of documents is in question, the courts have always proceeded, justifiably, on the basis that the overwhelming majority of people in this country will comply with the court’s order, and that defendants will therefore comply with orders to, for example, produce and deliver up documents without it being necessary to empower the plaintiffs’ solicitors to search the defendant’s premises.”
“Even in cases in which the plaintiff has strong evidence that an employee has taken what is undoubtedly specific confidential information, such as a list of customers, the court must employ a graduated response. To borrow a useful concept from the jurisprudence of the European Community, there must be proportionality between the perceived threat to the plaintiff’s rights and the remedy granted. The fact that there is overwhelming evidence that the defendant has behaved wrongfully in his commercial relationships does not necessarily justify an Anton Piller order. People whose commercial morality allows them to take a list of customers with whom they were in contact while employed will not necessarily disobey an order of the court requiring them to deliver it up. Not everyone who is misusing confidential information will destroy documents in the face of a court order requiring him to preserve them.”
“It has certainly become customary to infer the probability of disappearance or destruction of evidence where it is clearly established on the evidence before the Court that the defendant is engaged in a nefarious activity which renders it likely that he is an untrustworthy person. It is seldom that one can get cogent or actual evidence of a threat to destroy material or documents, so it is necessary for it to be inferred from the evidence which is before the Court.”
“If there was a genuine urgent threat to ISL’s business Mr Koppel would have acted in January or February when the Ebox Japanese deal was still a possibility.” b. There was no threat to destroy evidence. Although it is accepted that ISL always had a good claim to return of its property and to protection of its copyright by seeking an injunction, this is not a case where the claimant would have been deprived of that relief if notice of the claim had been given to the defendant. This was not therefore a case where a search order was essential to achieve justice between the parties and order for delivery up and injunction against breaching ISL’s copyright would have been adequate. This is, I think, a very bold submission in the light of (a) the constantly repeated denials, coupled with intemperate language, that the Defendants retained any computers or software belonging to ISL (b) the discovery of the mass of material on execution of the search order and (c) the less than frank disclosure afforded to the supervising solicitor and the attempted hiding of the server in the garden during the course of the search. c. In relation to the use of the Xenophon server, Mr Macdonald relies on answers given by Dr Waters in cross-examination to the effect that it looked increasingly unlikely by March 2005 that Xenophon might be used in the new product. But even he did not suggest that the possibility had been dismissed nor that possession of the source code might not be very useful in assisting in the development of the new product. d. Mr Macdonald also makes this submission: “It was put to [Mr Chandrasekaran] in cross examination that Dr Waters evidence about his email exchange with Stelios was about working with the Xenophon software, but changing it sufficiently so as to disguise it as a new product. He was asked if he accepted that evidence and said “Mostly I do, yes.”
“On our return to the UK, I now ask you and your son to leave us in peace. When in the past I have suggested that I want to inform the police of the threats you have made against us, you considered it a threat in itself to you and became quite cross (to put it mildly). I have now got to the stage where my family tells me that I have no choice but to inform the police should you continue. We are quite ill and I fear that my wife will never recover from this horrendous ordeal. Please leave us alone on our return.”
“Mr Koppel is…..My communications with Mr Koppel are very rarely by email, you know at that time. These were conversations. I want to be very clear about this because this is important. When he was saying to me that I could no longer work in this industry again [something, I interpose to note, that Mr Koppel denies ever saying] it was vexing me a lot, including the fact that he qualified that I could not even go back into research. He put a deal to me, that is that I have a£1 million debt, that I raise money and carry on with what I want to do. I had said to him at several times up until that, “People will not co-invest if they know you are involved”
“Neither of us [Mr Chandrasekaran and his wife] have anything to add to what I have stated to Mr Monty Koppel in my letter of 8th April. I insist that this correspondence from Kroll, which is clearly part of the intimidation process together with the Koppel’s, seize [sic] forthwith…”
“If you want to move on with your life it is now the time to be open and truthful”
“The essence of a clean-room development is that someone who is fully conversant with the software with which a compatible implementation is to be produced briefs the developer’s system analysts and they in turn produce a specification to which the new code is written…….The question might therefore be quite reasonably asked as to whether [Chandrasekaran] was sufficiently au fait with information security to be capable of specifying a product range for Ssaneva. Regular access and reference to the Indicii Salus software and reading the source code, manuals, etc. may have been important revision for a man who had been embroiled in management duties and away from the front line of his original trade for many years. The existing ISL code could be an important reference point not only at the initial stage of development of the specification of the new product, but also later. Once the Indians have developed a detailed specification, the existing source code could be referred to in order to improve upon or vary what the Indians produced. A further benefit might come from re-using the (perhaps confidential) cryptographic protocols utilised by Xenomail….This aspect of Xenomail design might be memorised and provide a head start to a clean-room developer…”
“Had encryption been his motive, he would have asked [Mr Koppel] for permission to do so and would not have engaged in the web of lies and deceit that has now been exposed”
“Overall it would make no sense for a new company, with fresh resources, and a new approach to systems building, to make use of ISL code from a technical point of view. From a business point of view it would be absolutely suicidal for Ssaneva to develop and attempt to market a product based on ISL code.”
“It is my view, absolutely preposterous to suggest that Paran will attempt to “copy”
“To conclude, throughout the development of the Ssaneva business plan, which I helped Paran with, and the lead up to and follow-up of the 21 June meeting, there was not even the scintilla of suspicion in my mind that the product which was to be at the heart of Ssaneva was anything other than a completely new product. If it is suggested by anyone that Paran was secretly holding out the possibility of somehow feeding Xenophon software to the Indian companies to work on in the new business, I would respond that this is inconceivable. These are multi-million pound listed companies whose business and whose customers are highly regulated. There is no way they would ever even contemplate touching another company’s product, and nor would they ever accept the say-so of an individual – however highly regarded – to the effect that it was his to hand over to them. Such an idea seems to me to be completely fanciful.” “I do not believe that there was a genuine risk that Paran would have used the ISL software in the new business because of all the safeguards put in place, such as the Technical Advisory Board, the involvement of the Indians, and the fact that the ultimate product would have been subjected to scrutiny by GCHQ and by sophisticated corporate end users, as well as the fact that the ISL software was sufficiently out-of date to be virtually unsalvageable.”
“….the current business which we are all working on, whilst still in the cryptographic space, will create a NEW server-centric cryptic engine with components and standards, which, I am told, are considerably different in some areas to anything that has gone before, In other words, not only will some of the components look different, but some of the design will also differ as a consequence of that. ……my lack of knowledge in this area means that I have to take [Mr Chandrasekaran’s] word about the extent of the changes to the components and the design. You will understand that much better…”; and he goes on to take comfort, even if that is wrong, from what he had been told by Mr Chandrasekaran to the effect that he, Mr Chandrasekaran, would be allowed to “use his brain and intellect to operate within a field in the public domain”
“I advised Paran in relation to these concerns [Paran’s relations with Mr Koppel]. I told him that it was very important that he should not copy the Indicii Salus software, and I explained that it was not just direct copying that should be avoided, but that indirect copying could also infringe copyright (ie “copying” could occur even if he was not looking at the code as he wrote down a new version or translation of it). I explained that the usual way of avoiding infringement in these circumstances was to use clean room procedures whereby the person who was familiar with the code would provide to an experienced analyst a detailed oral description (using only their memory and their own expressions) of the functionality of each module. The analyst would never have sight of or have recited to him any of the original specifications, code, screen dumps or reports but would provide a functional description of the modules based on that description. The detailed specification and code would then be developed by other persons. Paran appeared to me to understand completely the advice that I gave him, and always made it clear to me that his intention was to develop a new product (and he has never indicated otherwise, even before the conversations I have described) using clean room procedures.”
“Mr Vishwakiran has also explained to me that he asked Mr Chandrasekaran during the course of their discussions whether his technical team could be provided with some documentation on the old Xenophon product. They wanted background material so that they would have a deeper understanding of a server-centric system by the time of the meeting in London. However, Mr Vishwakirin says that Mr Chandrasekaran refused to provide them with the material, explaining that, because the intention was to create entirely new, up to date and independent software, he did not want to risk tainting the exercise in any way by making the old material available to HCL.”
“…in early 2005 there was a proposed transaction with a Japanese consortium where negotiations were in an advanced stage with draft agreements in circulation for a transaction at a consideration of approximately£9,000,000 . The draft agreement is exhibited to an affidavit made by Nigel Spence, who was a representative of the Japanese consortium. The Japanese consortium did not enter into this agreement because of an internal division in the consortium.”
“…I led the negotiating team of a Hong Kong and Japanese consortium in negotiations with the receivers of ISL for the purchase of the Xenophon software. During the course of these negotiations we carried out due diligence on the software and a price was finally agreed for the sale and purchase of the software with the receivers and the debenture holder of ISL in the sun of£9million ……The reason that the transaction did not proceed was because of a personal disagreement between Hong Kong and Japanese partners which was not related to either the software or the terms of the transaction referred to above.”
“This seems to be a mature and stable product and I have no doubt that if the product can be acquired for the right price it would be a sound acquisition for a company with an immediate route to a mass business market. I have no doubt that the technologists within the company are probably first class and absolutely vital to a rapid preparation of the product for new market places. I would see it as imperative to retain at least a nucleus of the technologists in the company in order to preserve the IP in a useable state.”
“I was aware, from Mr Soukup, that Baltimore was making several of its encryption software engineers redundant. I thought that I would be able to hire these to work on the ISL product, if I was successful in acquiring ISL. I prefer to hire new staff, who would be loyal to me, rather than inherit existing staff, whom I thought would be disgruntled and possibly disloyal.”
“In short, I am not convinced that [ISL] ever had a viable business, or that Ssaneva has now. The promoters of these companies have shown skill at selling equity but no skill at selling software – and little understanding of the markets in which they proposed to operate. There is some value in the software that [ISL] developed, but it does not relate to the defendants’ vision of “server-centric cryptography”