Abdul Latif Ibrahimi
Abdul Latif Ibrahimi is the former Governor of the Afghan Provinces Kunduz, Samangan, Faryab and Takhar. Abdul Latif Ibrahimi is member of the Ibrahims Clan, a predominant family in the Imam Sahib district in Kunduz. Imam Sahib is situated on the border with Tajikistan. It is a fertile agrarian district. Accordingly, the district is strategically very significant. The people of imam saheb love the Ibrahimi, he is very hamble person .[1] After the war Abdul Latif Ibrahimi became Governor of the Province. He was removed two years later and served for a short term as Governor of Faryab and of Takhar.
Abdul Latif Ibrahimi | |
|---|---|
| Governor of Takhar, Afghanistan | |
| In office 13 October 2009 – 18 March 2010 | |
| Preceded by | Ghulam Qawis Abubaker |
| Succeeded by | Abdul Jabbar Taqwa |
| In office 9 July 2013 – 7 October 2015 | |
| Preceded by | Maj. Gen. Ahmad Faisal Begzad |
| Succeeded by | Yasin Zia |
| Governor of Faryab, Afghanistan | |
| In office 2004–2005 | |
| Preceded by | Enayatullah Enayat |
| Succeeded by | Aamir Latif |
| Governor of Kunduz, Afghanistan | |
| In office 2002–2004 | |
| Succeeded by | Engineer Mohammad Omar |
Notes
- Afghan Bios:Abdul Latif Ebrahimi Archived July 18, 2011, at the Wayback Machine
| Preceded by Ghulam Qawis Abubaker |
Governor of Takhar, Afghanistan 2009–2010 |
Succeeded by Abdul Jabbar Taqwa |
| Preceded by Enayatullah Enayat |
Governor of Faryab, Afghanistan 2004–2005 |
Succeeded by Aamir Latif |
| Preceded by [?] |
Governor of Kunduz, Afghanistan 2002–2004 |
Succeeded by Engineer Mohammad Omar |
gollark: Well, because I dislike being creepily surveiled. Though I mostly don't go to much effort.
gollark: As far as I know ISPs can't see that you connect to your own LAN.
gollark: You may only ask dishonest questions.
gollark: VPNs prevent ISPs from seeing all this except possibly to some extent #3, but the VPN provider can still see it, and obviously whatever service you connect to has any information sent to it.
gollark: Anyway, with HTTPS being a thing basically everywhere and DNS over HTTPS existing, ISPs can only see:- unencrypted traffic from programs/services which don't use HTTPS or TLS- the *domains* you visit (*not* pages, and definitely not their contents, just domains) - DNS over HTTPS doesn't prevent this because as far as I know it's still in plaintext in HTTPS requestts- metadata about your connection/packets/whatever- also the IPs you visit, but the domains are arguably more useful anyway
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.