Thursday August 16, 2018
Home Uncategorized After Surgica...

After Surgical Strike, Pakistan Violated Ceasefire 286 times along LoC and IB in Jammu and Kashmir

The India-Pakistan ceasefire agreement of 2003 has virtually become redundant with 286 incidents of firing and shelling along LoC and IB in Jammu and Kashmir by the Pakistani troops

0
//
161
Representational image. Pixabay
Republish
Reprint

Jammu, November 13, 2016: The India-Pakistan ceasefire agreement of 2003 has virtually become redundant with 286 incidents of firing and shelling along LoC and IB in Jammu and Kashmir by the Pakistani troops.

NewsGram brings to you latest new stories in India

It has resulted in death of 26 people which includes 14 security personnel, since the surgical strike on terrorist launch pads in PoK.

According to PTI, “There have been 186 ceasefire violations by Pakistani troops along the over 190km International Border (IB) in Jammu frontier, while 104 violations of the agreement took place along the over 500km Line of Control (LoC).”

A senior BSF officer told, “There has been 182 ceasefire violation by Pak Rangers along IB targeting civilian areas and BoPs in Kathua, Samba and Jammu districts since the surgical strike on the intervening night September 28 and 29.”

Go to NewsGram and check out news related to political current issues

“They also resorted to firing of 120 mortar bombs and from automatic weapons very heavily in which civilians and security personnel were killed and a large number of people including women and children suffered injuries,” he said.

Due to heavy firing and shelling, a large population in the border areas were badly affected. A large number of cattle perished in the shelling and huge damage were caused to houses.

In 2003, India and Pakistan entered into no-firing agreement along Indo-Pak border in Jammu and Kashmir.

Look for latest news from India in NewsGram

On November 25, 2003, the Director Generals of Military Operations of India and Pakistan agreed to observe a ceasefire along the Line of Control, International Border, and Actual Ground Position Line in Jammu and Kashmir.

by NewsGram team with PTI inputs

Click here for reuse options!
Copyright 2016 NewsGram

Next Story

Aadhaar Helpline Mystery: French Security Expert Tweets of doing a Full Disclosure Tomorrow about Code of the Google SetUP Wizard App

0
Google Along with Other SSocial Media Giants will Face The Lawmakers, Wikimedia Commons
Google Along with Other SSocial Media Giants will Face The Lawmakers, Wikimedia Commons

Google’s admission that it had in 2014 inadvertently coded the 112 distress number and the UIDAI helpline number into its setup wizard for Android devices triggered another controversy on Saturday as India’s telecom regulator had only recommended the use of 112 as an emergency number in April 2015.

After a large section of smartphone users in India saw a toll-free helpline number of UIDAI saved in their phone-books by default, Google issued a statement, saying its “internal review revealed that in 2014, the then UIDAI helpline number and the 112 distress helpline number were inadvertently coded into the SetUp wizard of the Android release given to OEMs for use in India and has remained there since”.

Aadhaar Helpline Number Mystery: French security expert tweets of doing a full disclosure tomorrow about Code of the Google SetUP Wizard App, Image: Wikimedia Commons.

However, the Telecom Regulatory Authority of India (TRAI) recommended only in April 2015 that the number 112 be adopted as the single emergency number for the country.

According to Google, “since the numbers get listed on a user’s contact list, these get  transferred accordingly to the contacts on any new device”.

Google was yet to comment on the new development.

Meanwhile, French security expert that goes by the name of Elliot Alderson and has been at the core of the entire Aadhaar controversy, tweeted on Saturday: “I just found something interesting. I will probably do full disclosure tomorrow”.

“I’m digging into the code of the @Google SetupWizard app and I found that”.

“As far as I can see this object is not used in the current code, so there is no implications. This is just a poor coding practice in term of security,” he further tweeted.

On Friday, both the Unique Identification Authority of India (UIDAI) as well as the telecom operators washed their hand of the issue.

While the telecom industry denied any role in the strange incident, the UIDAI said that he strange incident, the UIDAI said that some vested interests were trying to create “unwarranted confusion” in the public and clarified that it had not asked any manufacturer or telecom service provider to provide any such facility.

Twitter was abuzz with the new development after a huge uproar due to Telecom Regulatory Authority of India (TRAI) Chairman R.S. Sharma’s open Aadhaar challenge to critics and hackers.

Ethical hackers exposed at least 14 personal details of the TRAI Chairman, including mobile numbers, home address, date of birth, PAN number and voter ID among others. (IANS)

Also Read: Why India Is Still Nowhere Near Securing Its Citizens’ Data?