Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
1 IN THE HIGH COURT OF JUDICATURE AT MADRAS DATED: 20.11.2018 CORAM: THE HON'BLE MR.JUSTICE S.MANIKUMAR AND THE HON'BLE MR.JUSTICE SUBRAMONIUM PRASAD W.P.No.30676 of 2018 and W.M.P.No.35778 of 2018 R.Renu Karthick ... Petitioner vs. 1.The Inspector General of Coast Guard The Indian Coast Guard, East Coast Guard Region No.5, GM Pettai Road, Royapuram, Chennai - 600 013. 2.The State of Tamilnadu, Represented by its Secretary to Government, Environment and Forest Department, Fort St. George, Secretariat, Chennai. 3.The Chairman, The Kamarajar Port Trust, No.17, Jawahar building, 2nd north wing and 3rd Floor, Rajaji Rd, Chennai 600001. 4.The Pollution Controal Board No.76, Anna Salai, Guindy, Chennai - 600032. 5.Owners and Parties interested in vessel MT Coral Stars http://www.judis.nic.in Now lying at Kamarajar Port, Chennai. ... Respondents 2 Prayer: Writ Petition is filed under Article 226 of the Constitution of India, praying for the issuance of a writ of Mandamus, directing the respondents 1 to 4 take action against the 5th respondent vessel and to take steps for initiating the prosecution and to recover costs and compensation. For Petitioner : Mr.N.Nandakumar For R1 : Mr.M.Aravind Kumar For R2 : Mr.S.V.Vijayaprashanth AGP (Forest) For R3 : Mr.Krishna Ravindran For R4 : Mr.Abdul Saleem For R5 : No Appearance ORDER
(Order of the Court was made by S.MANIKUMAR, J) On the basis of the newspaper item reported on 19.11.2018 in the Indian Express, stating that there is oil spill at Marine Liquid Terminal-1, at Kamarajar Port, Chennai, consequent to which, there is environmental pollution, loss of marine lives, fishermen unable to venture out for fishing, no action has been taken, as per the National Oil Spill Disaster Contingency Plan (NOS-DCP), against the fifth respondent, described to be the Owners and Parties interested in vessel MT Coral Stars, Kamarajar Port, Chennai, claiming himself to be http://www.judis.nic.in 3 a public interest litigant, and arraying respondent Nos.1 to 5, the petitioner has filed the instant writ petition, for a Mandamus, directing the respondents 1 to 4, to take action against the 5th respondent, to take steps for initiating prosecution and to recover costs and compensation.
2. Added further Mr.N.Nandakukar, learned counsel for the petitioner, submitted that the police has not registered any case and an e-mail dated 19.11.2018, has been sent by the petitioner to the respondents 1 and 2.
3. According to him, as per Sections 14 and 15 of the Merchants Shipping Act, 1958, Coast Guard, has a duty to register a compliant, within the jurisdictional police and proceed further, when there is a violation of the provisions of the Pollution Control Act and environmental pollution, due to the spillage of oil.
4. When the matter came up in the forenoon, the petitioner sought for an urgent order for detaining vessel MT Coral Stars, owned by fifth respondent, and take action under the provisions of Merchant Shipping Act, 1958.
http://www.judis.nic.in 4
5. In the forenoon, when the matter came up for admission, on instructions, Mr.Abdul Saleem, learned counsel for the Pollution Control Board/fourth respondent herein, submitted that on receipt of information from Coast Guard, Chennai/first respondent herein, and having regard to extent of spillage reported, Tamil Nadu Pollution Control Board, Chennai/respondent No.4 taken action.
6. Mr.S.V.Vijayprashanth, learned counsel for the Inspector General of Coast Guard, Indian Coast Guard, Chennai/respondent No.1, submitted that action has also been taken by the Coast Guard under the provisions of the Merchant Shipping Act, 1958. Thus, when oral submissions were made in the forenoon, we directed the learned counsel, to substantiate the same.
7. When the matter was taken up in the afternoon, Mr.S.V.Vijayprashanth, learned counsel for appearing Inspector General of Coast Guard, Indian Coast Guard, Chennai/first respondent, submitted that notice under Section 356(j) of the Merchant Shipping Act, 1958, has been issued to the fifth respondent.
He further submitted that Government of India, Ministry of Shipping, Directorate General of Shipping, Mumbai, has also taken action, under http://www.judis.nic.in 5 Section 356 (K)(2) of the Merchant Shipping Act, 1958, and issued notice to Owners and Parties interested in vessel MT Coral Stars/fifth respondent herein.
8. Mr.Krishna Ravindran, learned counsel appearing for Chairman, Kamarajar Port Trust, Chennai/third respondent herein, submitted that even before the writ petition was filed, action has been taken on 18.11.2018 itself, on the intimation from the Inspector General of Coast Guard, Indian Coast Guard, Chennai/first respondent herein and thus, there is no fault on the part of the first respondent in reporting and taking action.
9. Submission of the learned counsel for respondent Nos. 1, 3 and 4 respectively are placed on record.
10. Heard the learned counsel for the parties.
11. Instant writ petition, has been filed on 19.11.2018 by Mr.R.Renu Karthick, claiming himself to be a public interest litigant, for the prayers stated supra.
http://www.judis.nic.in 6
12. From the notice issued under Section 356(J) of the Merchant Shipping Act, 1958, it could be seen that no sooner there was a oil spill alongside MLT berth, Ennore, due to rupture of hose while discharging at 05.35 Hrs on 18 Nov, 2018 within Ennore port limits, which resulted in Oil spillage which threatened the coastal area, on 18.11.2018 itself, Coast Guard, has reported the same to the Chief Secretary to the Government of Tamil Nadu, Director General of Shipping, Mumbai, Marine Rescue Co-ordination Centre, Chennai, Chairman, Kamarajar Port, Ennore and Principal Secretary & Chairman, State Pollution Control Board, by Fax massages.
13. E-mail has also been sent to the Master, MT Coral Stars, about the coast oil spillage.
14. Section 358 of the Merchant Shipping Act, 1958, reads thus:-
"358. Shipping casualties and report thereof.— (1). For the purpose of investigations and inquiries under this Part, a shipping casualty shall be deemed to occur when —
(a) on or near the coasts of India, any ship is lost, abandoned, stranded or materially damaged; http://www.judis.nic.in
(b) on or near the coasts of India, any ship 7 causes loss or material damage to any other ship;
(c) any loss of life ensues by reason of any casualty happening to or on board any ship on or near the coasts of India;
(d) in any place, any such loss, abandonment, stranding, material damage or casualty as above mentioned occurs to or on board any Indian ship, and any competent witness thereof is found in India;
(e) any Indian ship is lost or is supposed to have been lost and any evidence is obtainable in India as to the circumstances under which she proceeded to sea or was last heard of.
(2) In the cases mentioned in clauses (a), (b) and
(c) of sub-section (1), the master, pilot, harbour master or other person in charge of the ship, or (where two- ships are concerned) in charge of each ship at the time of the shipping casualty, and in the cases mentioned in clause (d) of sub-section (1), where the master of the ship concerned or (except in the case of a loss) where the ship concerned proceeds to any place in India from the place where the shipping casualty has occurred, the master of the ship, shall, on arriving in India, give immediate notice of the shipping casualty to the officer appointed in this behalf by the Central Government."
15. Notice under Section 356(J) of the Merchant Shipping Act, 1958, dated 18.11.2018, issued by Commandant, Regional Fisheries http://www.judis.nic.in 8 and Environment Officer for Commander, Coast Guard Region (East), to M/s Atlantic Shipping Private Limited, Chennai and the Master, MT Coral Stars, is extracted hereunder:-
"NOTICE UNDER SECTION 356(J) OF MERCHANT SHIPPING ACT
1. Whereas it has come to the notice of Indian Coast Guard that the MT Coral Stars (IMO: 9286061, Flag: Marshall Islands) chartered by M/s Atlantic Shipping Pvt Ltd, Chennai has caused oil spill alongside MLT berth, Ennore reportedly due to rupture of hose whilst discharging at 0535 h on 18 Nov 18 within Ennore port limits resulted in Oil spillage which threatens the coastal area.
2. Further, initial assessment revealed that the port had taken few measures to contain the oil spill however, the ship and her agents have not yet taken suitable measures to remove the spill of approx. 01 Ton of FFO.
3. With the powers conferred upon to the Officers of the Indian Coast Guard under section 356(J) of the part XIA of Indian Merchant Shipping Act 1958, this notice for cleanup is hereby served to the owner/charterer/authorized agent for cleanup of spilled oil and for undertaking following actions:-
(a) Undertake containment and recovery of Oil spilled.
http://www.judis.nic.in (b) Take all other necessary action to keep 9 the environment clean as it was prevailing before the incident.
(c) Take necessary action to prevent further spillage of oil into the sea including removal of oil from the damaged tanks by transfer.
3. The Oil spill likely to drift towards coast which is likely to affect the coast line. Hence, you are advised to undertake above remedial action either through local agent or other agencies. Non compliance of the same will entail this Headquarters to take action under Section 356(K) of the XIA of Indian Merchant Shipping Act 1958.
4. The action taken report be intimated to Ennore Port under intimation to this Headquarters."
16. Government of India, Ministry of Shipping, Directorate General of Shipping, Mumbai, has taken action under Section 356(k)(2) of the Merchant Shipping Act, 1958 and Nautical Surveyor-cum-Deputy Director General (Tech), Mumbai, and issued notice in F.No.-
2NT(8)OPM/2018, dated 18.11.2018, to Master/owner/charterer/authoirzed agent/P71 insurer/local correspondent for P&1 insurer/and all other persons interested in the vessel MT Coral Stars and Bharat Petroleum Corporation Limited. For http://www.judis.nic.in brevity the same is extracted hereunder:-
10"NOTICE Sub: - Oil spill incident on 18.11.2018 from the vessel MT Coral Stars (IMO: 9286061. Flag: Marshall Islands) - notice under section 356(K)(2) of the Merchant Shipping Act, 1958 - reg.
Whereas, the Indian Coast Guard (ICG) issued notice under section 356(J) of the Merchant Shipping Act, 1958, vide fax [f.no.7585] dated 18.11.2018, to the Master / owner / charter / agent of vessal MT Coral Stars (IMO: 9286061], Flag: Marshall Islands), for clean- up of spilled oil, to undertake containment and recovery of oil spilled and other necessary action to keep the environment clean, as it was prevailing before the incident and to prevent further spillage of oil into the sea including removal of oil from the shore due to the pollution damage caused due to the oil spill incident from vessel 'MT Coral Stars' (IMO: 9286061).
2. And whereas, even though notice under 356(J) of the Merchant Shipping Act, 1958, was issued vide fax [f.no.7585] dated 18.11.2018, it was noticed that the oil escaped into the port waters, requiring urgent action to be taken by the authorities/agencies to deal with the pollution damage.
3. Now, therefore, as provided under the provision of subsection (2) of section 356(K) of the Merchant Shipping Act, 1958, all expenses and liabilities incurred for dealing with the said pollution incident shall be debt to the Central Government by the said vessel 'MT Coral Stars' (IMO: 9286061), its Master, owner, charterer, agent and all other persons interested in the vessel and all persons interested in the cargo, which is required to be paid at the earliest.
4. The Master, owner, charterer, agent and all other persons interested in the vessel and all persons interested in the cargo shall continue to take all necessary measures to prevent and mitigate the pollution damage caused due to the incident and restore http://www.judis.nic.in the environment to its original condition.
11Yours faithfully, (Capt. Anish Joseph) Nautical Surveyor-cum-
Dy. Director General (Tech)"
17. On the information from Coast Guard dated 18.11.2018, Pollution Control Board, Chennai, has acted swiftly and in exercise of the powers conferred under Section 32 of Water (P&CP) Act, 1974 as amended in 1988, Tamil Nadu Pollution Control Board has issued directions under Section 33(A) of Water (P&CP) Act, 1974, for detaining of the vessel MT Coral Stars.
18. Section 33A of Water (P&CP) Act, 1974, reads thus:-
"33A. Power to give directions.—Notwithstanding anything contained in any other law, but subject to the provisions of this Act, and to any directions that the Central Government may give in this behalf, a Board may, in the exercise of its powers and performance of its functions under this Act, issue any directions in writing to any person, officer or authority, and such person, officer or authority shall be bound to comply with such directions. Explanation.—For the avoidance of doubts, it is hereby declared that the power to issue directions under this section includes the power to direct - http://www.judis.nic.in 12
(a) the closure, prohibition or regulation of any industry, operation or process; or
(b) the stoppage or regulation of supply of electricity, water or any other service."
19. Proceedings of the Tamilnadu Pollution Control Board, Chennai, dated 19.11.2018, directing detention of the vessel and further directions, is reproduced hereunder:-
"TAMIL NADU POLLUTION CONTROL BOARD Proceedings No.: T5 /TNPCB / CHN / F.030569 / GMP / Oil spill / 2018, dated: 19.11.2018 Sub.: TNPCB - Spillage of furnace oil consigned to M/s.
Bharat Petroleum Corporation Limited into harbour waters inside M/s. Kamarajar Port at the Jetty of M/s. Ennore Tank Terminal Pvt Limited during discharge of furnace oil by ship M/s. Coral Stars, Ennore on 18.11.2018 - Directions issued under Provisions of Section 32 and 33 A of Water (Prevention and Control of Pollution) Act, 1974 - Regarding.
Ref.: 1. Water (Prevention & Control of Pollution) Act, 1974 as amended.
2. The Hazardous and Other Wastes (Management & Transboundary) Rules, 2016
3. Letter No. DEE / TNPCB / GMP / ETTPL / oil spill - 2 / dated: 18.11.2018
------
Whereas, the Water (Prevention and Control of Pollution) Act, 1974 as amended in 1988 is in force in Tamil Nadu. Tamil Nadu Pollution Control Board enforces the above Act.
http://www.judis.nic.in Whereas, Tamil Nadu Pollution Control Board has 13 been informed vide reference 3rd cited that out of the total quantity of 16000 KL of furnace oil consigned to M/s. Bharat Petroleum Corporation Limited there was a spillage of 1.5 Tons of furnace oil during pipe line transfer into the harbour waters inside M/s. Kamarajar Port at the Jetty of M/s. Ennore Tank Terminal Pvt Limited when the consignment was pumped and unloaded from the ship M/s. Coral Stars, Ennore on 18.11.2018 at 04:30 hrs. Whereas the cause of the spill is attributed to a shear at ferrule joint in 8” unloading hose pipe which connects the vessel (ship) and the unloading pipeline leading to ETTPL (Ennore Tank Terminal Pvt Ltd). Due to sudden failure in the hose pipe, around 1.5 tons of furnace oil has spilled in the sea water between the jetty and vessel (ship). As soon as the failure occurred in the hose pipe, unloading of furnace oil operation was reported to be stopped immediately.
The spillover of furnace oil is, reported to have been contained within 50 meters, since the boom has already been provided for containment of oil spill over, if any, before starting the unloading operation. It is reported that the spilled oil of 95% have been removed by engaging various instruments like oil skimmers, absorption pads etc. The spilled furnace oil (around 1.5 ton), collected from the sea has been kept in the jetty along with absorption pads. The spilled oil has been recovered by the port authorities using boom, oil skimmers and absorption pads. Saw dust has been poured http://www.judis.nic.in over the floor of the jetty for an area of about 10 square 14 meters, to remove the oil spillage in the jetty platform. The oil traces has been further removed by the port authorities using oil spill dispersants.
Whereas the damage caused to marine environment due to spillage of furnace oil has to be assessed and the liability is required to be fixed to all the agencies who were involved in the said operations resulting in spillage of furnace oil in to the marine waters.
Whereas, as per Section 24 of Water (Prevention And Control of Pollution) Act, 1974, no person shall knowingly cause or permit any poisonous, noxious or polluting matter determined in accordance with such standards as may be laid down by the State Board to enter (whether directly or indirectly) into any stream or well or sewer or on land.
Whereas, Section 32 of the said Act reads as follows “Emergency measures in case of pollution of stream or well (1) Where it appears to the State Board that any poisonous, noxious or polluting matter is present in [any stream or well or on land] by reason of the discharge of such matter in such stream or well or on such land] or has entered into that stream or well due to any accident or other unforeseen act or event, and if the Board is of opinion that it is necessary or expedient to take immediate action, it may for reasons to be recorded in writing, carry out such operations, as it may consider necessary for all or any of the following purposes, that is to say- (a) removing that matter from http://www.judis.nic.in the [stream or well or on land] and disposing it of in 15 such manner as the Board considers appropriate; (b) remedying or mitigating any pollution caused by its presence in the stream or well; (c) issuing orders immediately restraining or prohibiting the person concerned from discharging any poisonous, noxious or polluting matter 27[into the stream or well or on land] or from making insanitary use of the stream or well".
Whereas, Rule 2 - 39 of the Hazardous & Other Wastes (Management & Transboundary Movement) Rules, 2016 defines waste oil as, "waste oil means any oil which includes spills of crude oil, emulsions, tank bottom sludge and slop oil generated from petroleum refineries, installations or ships and can be used as fuel in furnaces for energy recovery, if it meets the specifications laid down in Part-B of Schedule V either as such or after reprocessing.
Whereas, Rule 23(1 )&(2) of the Hazardous & Other Wastes (Management & Transboundary Movement) Rules, 2016 reads as follows, “Liability of occupier, importer or exporter and operator of a disposal facility 23 - (1) The occupier, importer or exporter and operator of the disposal facility shall be liable for all damages caused to the environment or third party due to improper handling and management of the hazardous and other wastes 23 - (2) The occupier and the operator of the disposal facility shall be liable to pay financial penalties as levied for any violation of the provisions under these rules by the State Pollution Control Board with the prior http://www.judis.nic.in approval of the Central Pollution Control Board”.
16Now therefore in exercise of the powers conferred under Section 32 of the Water (P&CP) Act, 1974 as amended in 1988, Tamil Nadu Pollution Control Board issues the following directions to you under Section 33A of Water (P&CP) Act 1974 as amended, as you are one of the agencies involved in the said operation which resulted in spillage of furnace oil into the marine waters:
1. The ship M/s. Coral Star shall be detained till the liability is fixed and necessary compensation for the expenses incurred / to be incurred towards remediation of the marine environment affected due to the said spillage of furnace oil needs to be assessed and deposited as per the Polluter pays Principle”.
2. To take all necessary action for complete remedy of the negative environmental impact of this spill immediately.
3. The remnants of the oil spill collected from the harbour waters and the contaminated saw dust used for absorption to clean and remove the oil spilled in the jetty platform shall be stored in compatible containers in designated storage yards with requisite safety precautions till it is safely disposed as per the provisions of Hazardous and Other Wastes (Management and Transboundary Movement) Rules, 2016.
The status of action taken in complying with the http://www.judis.nic.in directions shall be intimated to this office within a 17 week’s time."
20. Chapter III of the Indian Coast Guard Act, 1978, is extracted hereunder:-
"Chapter III DUTIES AND FUNCTIONS OF THE COAST GUARD
14. (1) It shall be the duty of the Coast Guard to protect by such measures, as it thinks fit, the maritime and other national interests of India in the maritime zones of India, (2) -Without prejudice to the generality of the provisions of subsection (1), the measures referred to therein may provide for -
(a) ensuring the safety and protection of artificial islands, offshore terminals, installations and other structures and devices in any maritime zone;
(b) providing protection to fishermen including assistance to them at sea while in distress;
(c) taking sueh measures as are necessary to preserve and protect the maritime environment and to prevent and control marine pollution;
(d) assisting the customs and other authorities in anti-smuggling operations;
(e) enforcing the provisions of such enactments as are for the time being in farce in the maritime zones; and
(f) such other matters, including measures for the safety of life and property at sea and collection http://www.judis.nic.in of scientific data, as may be prescribed.18
(3) The Coast Guard shall perform its functions under this section in accordance with, and subject to such rules as may be prescribed and such rules may, in particular, make provisions for ensuring that the Coast Guard functions in close liaison with Union agencies, institutions and authorities so as to avoid duplication of effort."
21. Inter alia the contentions made by Mr.N.Nandakumar, learned counsel for the petitioner, is that Coast Guard has a duty to register a complaint and take action. Thus there is a failure, for which, he sought for a direction against the respondents 1 to 4, for initiating the prosecution and to recover costs and compensation.
22. Chapter IV and V of the Indian Coast Guard Act, 1978, deals with offences and punishments respectively, and the same are extracted hereunder:-
"CHAPTER.IV OFFENCES
15. Any person subject to this Act. who,-
(a) treacherously holds correspondence with, or communicates intelligence to, an offender; or
(b) wilfully fails to make known to the proper authorities any information he may have received from an offender; or http://www.judis.nic.in 19
(c) having been captured by an offender, voluntarily serves with or aids him, shall, on conviction by a Coast Guard Court, be liable to suffer imprisonment for a term which may extend to seven years or such less punishment as is in this Act mentioned.
Explanatian.- For the purposes of this section, "offender" includes-
(a) all armed mutineers, armed rebels, armed rioters, pirates and any person in arms against whom it is the duty of any person subject to this Act to take action; and
(b) any person or persons engaged in smuggling, unlawful exploration or exploitation or any other unlawful activity in the maritime zones of India.
CHAPTER V PUNISHMENTS
53. (1) Punishments may be inflicted in respect of offences committed by persons subject to this Act and convicted by Coast Guard Courts according to the scale following, that is to say,-
(a) death;
(b) imprisonment which may be for the term of life or any other lesser term;
(c) dismissal from the Coast Guard;
(d) detention in Coast Guard custody for a period not exceeding two years;
(e) reduction to the ranks or to a lower rank in http://www.judis.nic.in the case of sailors;20
(f) forfeiture of seniority of rank, forfeiture of all or any part of the service for the purpose of promotion;
(g) forfeiture of service for the purpose of increased pay, pension or any other prescribed purpose;
(h) fine, in respect of civil offences;
(i) mulcts of pay and allowances;
(j) severe reprimand or reprimand except in the case of persons below the rank of an Uttam Navik or Uttam Yantrik.
(2) Each of the punishments specified in sub- section (1) shall be deemed to be inferior in degree to every punishment preceding it in the above scale.
54. Subject to the provisions of this Act, a Coast Guard Court may, on convicting a person subject to this Act of any of the offences specified in sections 15 to 48 (both inclusive) award either the particular punishment with which the offence is stated In the said sections to be punishable, or in lieu thereof, anyone of the punishments lower in the scale set out in section 53 regard being had to the nature and degree of the offence.
55. Subject to the provisions of section 58, a sentence of a Coast Guard Court may award in addition to, or without anyone other punishment, the punishment specified in clause (c) of sub-section (1) of section 53 and anyone or more of the punishments specified in clauses
(e) to (j) (both inclusive) of that sub-section.
http://www.judis.nic.in
56. Punishments may also be inflicted in respect 21 of offences committed by persons subject to this Act without the intervention of a Coast Guard Court in the manner stated in section 57.
57. Subject to the provisions or section 58, a Commanding Officer or such other officer as is, with the consent of the Central Government, specified by the Director-General may, in the prescribed manner, proceed against a person subject to this Act, otherwise than as an officer, who is charged with an offence under this Act and award such person, to the extent prescribed, one or more of the following punishments, that is to say,-
(a) imprisonment for a period not exceeding three months;
(b) dismissal from the Coast Guard;
(c) detention in Coast Guard custody for a period not exceeding three months;
(d) reduction to the ranks or to a lower rank in the case of sailors;
(e) fine, in respect of civil offences;
(f) mulcts of pay and allowances;
(g) deprivation of good conduct badges;
(h) reprimand;
(i) extra work and drill for a period not exceeding fourteen days in the case of persons below the rank of an Uttam Navik or Uttam Yantrik:
(j) stoppage of leave for a period not exceeding sixty days;
(k) admonition;
http://www.judis.nic.in Provided that no punishment specified in clauses 22
(a) to (d) (both inclusive) shall be inflicted,-
(a) in the case of a subordinate officer, unless it is approved by an officer not below the rank of an Inspector-General; and
(b) in the case of others, unless it is approved by an officer not below the rank of a Deputy Inspector-General.
58. (1) The punishments that may be inflicted under this Act shall be awarded in accordance with the provisions of this section.
(2) A sentence of imprisonment under this Act shall in all cases be accompanied by a sentence of dismissal.
(3) A sentence of imprisonment may be rigorous or simple or partly rigorous and partly simple.
(4) No officer shall be subject to detention for any offence under this Act.
(5) No subordinate officer shall be sentenced to detention except for desertion.
(6) A sentence of detention shall not be accompanied by a sentence of dismissal from the Coast Guard.
(7) A sentence of detention for a period exceeding fourteen days shall in all cases be accompanied by stoppage of pay and allowances during the period of detention."
23. Reading of the provisions, does not make it obligatory on the part of the Coast Guard to register any compliant within the http://www.judis.nic.in 23 jurisdictional police. In the light of the statutory provisions, contention of the learned counsel for the petitioner, cannot be countenanced.
24. Inspector General of Coast Guard, Indian Coast Guard, Chennai; Chairman, Kamarajar Port Trust, Chennai and Pollution Control Board, Chennai, respondents 1, 3 and 4 respectively, have discharged their duties immediately and taken appropriate action.
Relief sought for by the petitioner has been addressed by the respondents, and hence no further direction is required in the instant writ petition.
25. Mr.Abdul Saleem, learned counsel for the Pollution Control Board, Chennai/third respondent, submitted that 90% of cleaning of oil spillage, has already been over and removal of the remaining oil spillage, would be completed within two days.
26. In view of the above, writ petition is dismissed. No Costs.
Consequently, the connected writ miscellaneous petition is closed.
http://www.judis.nic.in (S.M.K., J.) (S.P., J.) 24 20.11.2018 Index: Yes/No Internet: Yes/No dm Note:-
Issue order copy on or before 22.11.2018 http://www.judis.nic.in 25 To
1.The Inspector General of Coast Guard, The Indian Coast Guard, East Coast Guard Region No.5, GM Pettai Road, Royapuram, Chennai - 600 013.
2.The Secretary to Government, State of Tamilnadu, Environment and Forest Department, Fort St. George, Secretariat, Chennai.
3.The Pollution Controal Board, No.76, Anna Salai, Guindy, Chennai - 600032.
http://www.judis.nic.in 26 S.MANIKUMAR,J.
AND SUBRAMONIUM PRASAD, J.
dm W.P.No.30676 of 2018 and W.M.P.No.35778 of 2018 20.11.2018 http://www.judis.nic.in


Guidance on creating new requirements
The first stage in proposing a requirement to the Digital Prototyping Unit is to enter
a high level summary including:
A brief summary
- this will help us figure out what we need to do and what technology to use
The anticipated
benefits IMPORTANT - the benefits are used to prioritise projects.
The WBS code and target completion date
What if I dont
have a WBS Code? If you don't have a WBS code, we will work on your requirement using bench resource. In
this case, we can not guarantee a delivery date and the prototype will not be production ready (e.g. we wont
security test it etc.)
When are ready to propose your requirement, press submit
Submission check list
By submitting this requirement you are confirming that:
To the best
of your knowledge, the benefits articulated above are reasonable and will be achieved within 12 months.
You have set
up a document repository (under the documents tab on the left) and completed a requirements specification.
You will be
able to commit up to 3 hours a week to work with a Digital Prototyping Unit team on your requirement.
You
understand your role as Product Owner and have viewed the Intro to Product Ownership (on Youtube).


Seattle U claims WAC crown, beats Utah Valley in shootout
by Seattle Times staffThe No. 19 Seattle U men won the Western Athletic Conference soccer tournament Sunday afternoon in Colorado Springs, Colo.
Akili Kasim earned tournament MVP honors after making three saves in the shootout win against Utah Valley (13-6-2).
The game was tied 1-1 after regulation and overtime. Julian Avila-Good scored for the equalizer for the Redhawks (14-3-4) in the 43rd minute.
Seattle, which is on a 14-match unbeaten streak, won the shootout 2-1. It’s the fourth time the Redhawks have won the WAC tourney since 2013. They qualified for the NCAA tournament, and will find out their first-round opponent Monday morning.
The Washington men will also find out their NCAA fate as the NCAA selection show is 10 a.m. on NCAA.com.
Volleyball
• Pia Timmer had 16 kills, and Jocelyn Urias added 15 as Washington State (22-6, 11-5 Pac-12) beat visiting Colorado 25-23, 24-26, 13-15, 25-15, 15-9. Justine Spann had 16 kills and 10 digs for the Buffaloes (11-15, 3-13).
• Eve Kerschenbaum had 15 kills as Seattle U (13-16, 4-12 Western Athletic Conference) earned a road sweep against California Baptist, 25-18, 25-22, 25-21.
Hockey
• Wyatt Wylie scored in the second period and Gianni Fairbrother added an empty netter in the third period as the Everett Silvertips beat the visiting Spokane 2-0.
From sports-information reports.


sUTL Universal Transform Language
Source JSON
sUTL Transform
Result JSON
Info
Edit the Source and / or Transform, and the result updates automatically.
Editor built by Emlyn O'Regan, August 2015. It uses sUTL.js.
Edit the Source and / or Transform, and the result updates automatically.
Editor built by Emlyn O'Regan, August 2015. It uses sUTL.js.


Look at the picture. The number in the circle is less than l0. You say “5 is less than l0.”
Now look at the picture below. The number in the circle is more than 5. You say “10 is more than 5.”


Are there additional classes you'd like to add to your list?
Applied Linguistics
Bilingualism 452
Virgil and the Iliad


Here we go. This app was made to discover some Web Audio API features. Also, this is my 'Hello World' in Angular 2 and Typescript worlds.
Right now there are 3 instruments here: a simple monophonic synthesizer, a polyphonic one, both with a regular piano keyboard. And "experimental" one, I call it a "plot synth".
It's easy to hear that there are some bugs here: for example, I'm pretty sure that attack/release parameters don't work correctly. Anyway, later I will fix it when I add new parameters and concentrate on a sound process.


Settings
Browse
Cancel
Title
Subtitle
Choose a contact to add to Favorites
Contacts
Cancel
Choose multiple contacts to add to your Favorites so this just goes on and on and on
Groups
Contacts
Cancel


Breaking News!
Breaking news, also known as a special report or news bulletin, is a current issue that broadcasters feel warrants the interruption of scheduled programming and/or current news in order to report its details. Its use is also assigned to the most significant story of the moment or a story that is being covered live. It could be a story that is simply of wide interest to viewers and has little impact otherwise. Many times, breaking news is used after the news network has already reported on this story. When a story has not been reported on previously, the graphic and phrase "Just In" is sometimes used instead.
In early coverage of a breaking story, details are commonly sketchy, usually due to the limited information available at the time. For example, during the Sago Mine disaster, initial reports were that all twelve miners were found alive, but news organizations later found only one actually survived.
Another criticism has been the diluting of the importance of breaking news by the need of 24-hour news channels to fill time, applying the title to soft news stories of questionable importance and urgency, for example car chases. Others question whether the use of the term is excessive, citing occasions when the term is used even though scheduled programming is not interrupted.


Check out this interview with the world's oldest-known iPhone app developer
Source: Nikkei Asian Review
What you need to know
- Nikkei Asian Review has shared an interview with Masako Wakamiya.
- At 84-years-old, she is thought to be the world's oldest known iPhone app developer.
- She was even invited to WWDC by Apple, and Tim Cook said he found her "inspiring".
Nikkei Asian Review has shared an interview with Masako Wakamiya, who is thought to the world's oldest known iPhone app developer.
In the interview, she discussed topics including her first computer and her meeting with Apple CEO Tim Cook.
The report describes her saying:
Masako Wakamiya obtained her first personal computer at age 58, just ahead of her retirement from a bank. Little did she know that she was beginning a journey that would make her the world's oldest known iPhone app developer, at 81. Now 84, Wakamiya calls herself an IT evangelist and encourages other seniors to use digital technology to enrich their lives. She writes books while spreading her message on the lecture circuit in Japan and abroad.
Wakamiya discusses how she familiarised herself with early smartphones, and soon came up with the idea of a game based on Japan's annual doll festival, 'hinamatsuri'.
There were no apps that old people found amusing. I decided to make a game in which old people could beat young people. I thought that arranging dolls for the hinamatsuri would be a good concept. I drew up a plan and asked the president of an app development company in Miyagi Prefecture to produce the game. I had become acquainted with him through volunteering in the area hit by the March 2011 earthquake. He said, "May I suggest that you do it by yourself?" I wrote the program at home in Kanagawa Prefecture, while learning from him over Skype. The smartphone game, called Hinadan, was completed just before the hinamatsuri in 2017.
Coding an app at home whilst being guided over Skype by the president of an app development company would be a noble achievement for almost all of us, let alone an 81-year-old lady. Her endeavors gained her recognition to the point that she was contacted by Apple in Japan, who invited her to the U.S.
According to the report, she was told that someone "really wanted to meet her". Turns out it was, in fact, Apple CEO Tim Cook. Much to her surprise, he wanted to speak with her and look at her iPhone. She explained her app to him saying:
"Since senior citizens are not good at swiping... I made it possible for them to play by tapping."
Cook said he found Wakamiya inspiring, and introduced her to WWDC as the world's oldest programmer the next day.
Wakamiya also discussed her other pursuits, including making speeches and traveling. She describes herself as an IT evangelist, and her ideas include investment funds backed by senior citizens which can provide backing to young entrepreneurs who wish to start businesses. She also discussed using an AI speaker in her home, how technology can aid the elderly, and 'excel art', which is about using spreadsheet software to create designs. She says amidst all of this, her goal is to remain creative.
You can read the full interview here.


CrimPapers
Articles published on 13 February 2018
On 13 February 2018, 7 new articles were published in 7 journals.
Social Control Versus Social Learning: Self-Efficacy For Future Academic Success and Peer Delinquency As Mediators of the Parental Support–delinquency Relationship by Glenn D. Walters
Putting in Work: the Application of Identity Theory to Gang Violence and Commitment by Bryan F. Bubolz, Sou Lee
#metoo Must Include Prostitution
Neighborhood Context and Homicide Clearance: Estimating the Effects of Collective Efficacy by Ashley M. Mancik, Karen F. Parker, Kirk R. Williams
“…they Didn't Just Do It Because It Was A Job”: Representing Wardens in Canadian Penal History Museums
Familial Sex Trafficking of Minors: Trafficking Conditions, Clinical Presentation, and System Involvement
Confessions of A Criminal Psychopath: An Analysis of the Robert Pickton Cell-Plant


Canvi is a simple off-canvas navigation with a few parameter to configure. You can init multiple instances, set responsive width, use your style our Canvi's style.
To install Canvi get the JS and the CSS file and insert into your project. You can also customize the Sass to save some byte.
// To the head
<link rel="stylesheet" href="canvi.css">
// To the end of the body

To use Canvi first, you have to implement the correct HTML structure which is mean the proper use of the .canvi-navbar and .canvi-content.
<!DOCTYPE html>

After this you need to call the Canvi constructor and viola you are done!
var canvi = new Canvi();
To make multiple instances, you must specify the correct value for the content, navbar and openButton property. Note that the content can be the same on multiple initializations.
var canviLeft = new Canvi({
content: '.js-canvi-content',
navbar: '.js-canvi-navbar--left',
openButton: '.js-canvi-open-button--left'
});
var canviRight = new Canvi({
content: '.js-canvi-content',
navbar: '.js-canvi-navbar--right',
openButton: '.js-canvi-open-button--right'
});
Canvi using aria-hidden="true" when the navigation is hidden. If you want to be more accesible you can use the inert attribute - which is also used by Canvi - but for this you need to use this polyfill because it is quite a new feature. Just simply insert the script into your project.
If you like to know more about inert check out A11ycats #2 episode!
Type: string
Default: '.canvi-content'
This selector defines the content part of the markup. Mostly you need to modify this when you use multiple Canvi.
Type: boolean
Default: false
Canvi's debugger switch.
Type: string
Default: '.canvi-navbar'
Define the navbar part of the structure. This selector is part of the default markup. Mostly you need to modify it'value when you use multiple Canvi.
Type: string
Default: '0.3s'
You can specify here the opening/closing speed of the menu.
Type: string
Default: '.canvi-open-button'
Canvi open button selector.
Type: string
Default: 'left'
Specify the position of the navigation.
Type: boolean
Default: true
Set if you don't want the menu to push the content. In this case, it will lay over your page.
Type: string
Default: '300px'
Set the width of the navbar. You must give string with the correct unit so you can specify any value type like em, %, px.
Type: array
Default: []
With this option, you can modify the width of the navbar by breakpoints. This is a mobile first approach, and the very first width option will be width parameter's value.
Canvi comes with a few method so you can open and close it manually from your code. To use these methods, you must save the Canvi instance in a variable at the declaration like to following:
var canviRight = new Canvi({
content: '.js-canvi-content',
navbar: '.js-canvi-navbar--right',
openButton: '.js-canvi-open-button--right',
position: 'right',
pushContent: true,
width: '300px'
});
Open the Canvi instance.
canviRight.open();
Close the Canvi instance.
canviRight.close();
Toggle the Canvi instance.
canviRight.toggle();
Canvi came with custom events which you can use to customize, modify Canvi or your site's specific parts. To catch an event all you have to do is to define an event listener to the body element.
Each event gives back three additional Canvi elements named by navbar, openButton, content. You can access them through the event object like e.detail.navbar.
This event is triggered when Canvi initialization ready. To catch the initialization event, you have to watch the canvi.init event. Note that you must declare the following code before the Canvi constructor.
document.querySelector('body').addEventListener('canvi.init', function(e) {
console.log('Catch Canvi init event...');
});
This event is triggered when you click on the menu open button. To catch the before-open event, you have to watch the canvi.before-open event.
document.querySelector('body').addEventListener('canvi.before-open', function(e) {
console.log('Catch Canvi before-open event...');
});
This event is triggered after the menu opened. To catch the after-open event, you have to watch the canvi.after-open event.
document.querySelector('body').addEventListener('canvi.after-open', function(e) {
console.log('Catch Canvi after-open event...');
});
This event is triggered before you close the menu. To catch the before-close event, you have to watch the canvi.before-close event.
document.querySelector('body').addEventListener('canvi.before-close', function(e) {
console.log('Catch Canvi before-close event...');
});
This event is triggered after the menu closed. To catch the after-close event, you have to watch the canvi.after-close event.
document.querySelector('body').addEventListener('canvi.after-close', function(e) {
console.log('Catch Canvi after-close event...');
});


Current version: {{ version }}
Get Setuptools from the Python Package Index
Visit the Setuptools project page


| DOSE: T+ 0:00 |
10 mg |
smoked |
2C-T-2 |
(powder / crystals) |
| T+ 19:00 |
1 cig. |
smoked |
Cannabis |
(plant material) |
I want to keep it short. I have a lot experiences with different drugs, always being wise and doing a lot of research in front. This time I acquired 2C-T-2 and wanted to try smoking it. The sample came from a source I trust.
Setting: Safe
Set: Happy, needed some directions after long period of self-supported detox.
Smoke felt toxic and in 10 seconds I knew it will be a harsh ride. Visuals were pretty strong, Persian carpet type, typical for 2C's. Colors of objects were cycling, CEVs were strong, fast and frightening - of a unbelievable complex fractal type, which I would describe as multidimensional (more then in space, more then in time, there were dimensions coming into existence and disappearing randomly).
I've seen how the nature works. I learned how the stronger wins. And I've understood there are indefinite possibilities how to become the strongest and that there are no limitations. It's the universe... all the possibilities, no compromises. What happens can't be undone.
It was a long torture, where I was hunted by the stronger organisms. No matter what they were. I couldn't escape to safety, I couldn't accept what's happening in my mind. I had to accept that nothing is granted and that I there is no rest.
The strongest part of the experience, when I was completely paralyzed by the overwhelming psychedelia, took about 9 hours. Then I could see the world, the clock, understand what I am and rest a bit. I was not able to stand up for another 5 hours. At T+19:00 I went to have a joint with my little brother, but then the visuals returned, but this time in different manner, which was acceptable. I told him about the experience and told me I probably overdid it... very funny.
In the latter experiences I ingested 12 and 16mg and all were great. I even met my new girl friend thanks to this material, which helped me to find something I've lost in my life... or at least, she helped me to find the path to it again.
Thank you my fairy, I won't forget about you... :)
I advise against smoking this material, it decomposed quickly on the foil to a black dirt and the smoke tasted toxic. Not really healthy. Anyway, we're living only once, so reasonable dosage would be in my opinion between 0.5-3mg.
Good energy for all, let the universe take care about you.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


We have invested in all the latest specialist tools and diagnostic software that is specifically tailored for the software in your vehicle.
.We provide top notch maintenance service for all types of vehicles. We are certified to service and repair the following makes:
By registering on your website you can book you vehicle for service or repair online. Also you will be able to view your full service history.


The extraction of design pattern information from software systems can provide conspicuous insight to software engineers on the software structure and its internal characteristics. In this demonstration we present ePAD, an Eclipse plug-in for recovering design pattern instances from object-oriented source code. The tool is able to recover design pattern instances through a structural analysis performed on a data model extracted from source code, and a behavioral analysis performed through the instrumentation and the monitoring of the software system. ePAD is fully configurable since it allows software engineers to customize the design pattern recovery rules and the layout used for the visualization of the recovered instances.


This RPC allows to request diagnostic module trouble codes from a certain vehicle module
Function Group: ProprietaryData
HMILevel needs to be FULL, LIMITED or BACKGROUND
Convenience init
- (nonnull instancetype)initWithECUName:(UInt16)name;
init(ecuName name: UInt16)
Name of the module to receive the DTC form
An SDLGetDTCs object
Convenience init with all properties
- (nonnull instancetype)initWithECUName:(UInt16)name mask:(UInt8)mask;
init(ecuName name: UInt16, mask: UInt8)
Name of the module to receive the DTC form
DTC Mask Byte to be sent in diagnostic request to module
An SDLGetDTCs object
a name of the module to receive the DTC form @discussion an NSNumber value representing a name of the module to receive the DTC form
Notes: Minvalue:0; Maxvalue:65535
@property (nonatomic, strong) NSNumber<SDLInt> *_Nonnull ecuName;
var ecuName: NSNumber & SDLInt { get set }
DTC Mask Byte to be sent in diagnostic request to module. NSNumber* dtcMask Minvalue:0; Maxvalue:255
@property (nonatomic, strong, nullable) NSNumber<SDLInt> *dtcMask;
var dtcMask: (NSNumber & SDLInt)? { get set }


Access your public information.
Access your public and private information.
For private repositories and gists we only use information for skills, badges, and activity (event type only).
We will not store nor show any private information on your profile.


Between 2 and 4 August 2014, a total of 108 new cases of Ebola virus disease (laboratory-confirmed, probable, and suspect cases) as well as 45 deaths were reported from Guinea, Liberia, Nigeria, and Sierra Leone.
A mission briefing with representatives from Member States was held on 5 August at the World Health Organization (WHO). Information about the nature of Ebola virus disease (EVD) was highlighted. This was followed by outlining the essential components for control, including the need for national leadership, improved care and case management, identifying transmission chains and stopping disease spread, and preventing further outbreaks. Among the critical issues are: cross-border infections and travelers; partners reaching the limits of their capacity and ability to respond rapidly, safely, and effectively; and concerns about the socio-economic impact of continued transmission.
The Director-General also shared information from her recent meetings in Guinea with Member States of the Mano River Union – Côte d’Ivoire, Guinea, Liberia, and Sierra Leone. She outlined that the response in West Africa would focus on three areas:
The Sub-regional Ebola Operations Coordination Centre (SEOCC) in Conakry reported on 5 August that the following actions are underway in the four affected countries:
The SEOCC is assisting countries with these and many other response measures.
On 6 August, WHO is convening an Emergency Committee of international experts to review the outbreak and advise the Director-General, in accordance with the International Health Regulations, whether the Ebola virus disease outbreak constitutes a Public Health Emergency of International Concern (PHEIC). Experts will receive an epidemiological briefing and will determine whether the criteria for a PHEIC have been met. If the Emergency Committee agrees that this is a PHEIC, they will then advise the Director-General on temporary recommendations. A summary of the meeting will be made public and a press briefing will be held on Friday, 8 August.
New cases and deaths attributable to EVD continue to be reported by the Ministries of Health in Guinea, Liberia, Nigeria, and Sierra Leone. Between 2 and 4 August 2014, 108 new cases (laboratory-confirmed, probable, and suspect cases) of EVD and 45 deaths were reported from the four countries as follows: Guinea, 10 new cases and 5 deaths; Liberia, 48 new cases and 27 deaths; Nigeria, 5 new cases and 0 death; and Sierra Leone, 45 new cases and 13 deaths.
As of 4 August 2014, the cumulative number of cases attributed to EVD in the four countries stands at 1 711, including 932 deaths. The distribution and classification of the cases are as follows: Guinea, 495 cases (351 confirmed, 133 probable, and 11 suspected), including 363 deaths; Liberia, 516 cases (143 confirmed, 252 probable, and 121 suspected), including 282 deaths; Nigeria, 9 cases (0 confirmed, 2 probable, and 7 suspected), including 1 death; and Sierra Leone, 691 cases (576 confirmed, 49 probable, and 66 suspected), including 286 deaths.
| New | Confirmed | Probable | Suspect | Totals | |
| Guinea | |||||
| Cases | 10 | 351 | 133 | 11 | 495 |
| Deaths | 5 | 228 | 133 | 2 | 363 |
| Liberia | |||||
| Cases | 48 | 143 | 252 | 121 | 516 |
| Deaths | 27 | 128 | 110 | 44 | 282 |
| Nigeria | |||||
| Cases | 5 | 0 | 2 | 7 | 9 |
| Deaths | 0 | 0 | 1 | 0 | 1 |
| Sierra Leone | |||||
| Cases | 45 | 576 | 49 | 66 | 691 |
| Deaths | 13 | 247 | 34 | 5 | 286 |
| Totals | |||||
| Cases | 108 | 1 070 | 436 | 205 | 1 711 |
| Deaths | 45 | 603 | 278 | 51 | 932 |
| 1. New cases were reported between 2 and 4 August 2014. |
The total number of cases is subject to change due to reclassification, retrospective investigation, consolidation of cases and laboratory data, and enhanced surveillance. Data reported in the Disease Outbreak News are based on best available information reported by Ministries of Health.


R o s t e r
Name Nmaey
Intern
# 123
Email: email
School: school
Name Nmaey
Intern
# 123
Email:
email
School: school


---
layout: page
title: Orbit for DevRel and Community Teams
description: Orbit helps deliver a stellar member experience—and prove it.
eleventyNavigation:
key: DevRel and Community Teams
---
{% from "macros/typography.njk" import subhead, tagline, title %} {% from
"macros/buttons.njk" import get_started %}
{% from "macros/features.njk" import single_feature_with_image, double_feature_with_images %}
{{ title("Grow your community and show ROI.") }} {{ tagline(" Orbit helps
Developer Relations and Community Teams deliver a stellar member
experience—and prove it. ") }} {{ get_started(inverted=true) }}
{{ subhead("Never miss a moment.") }}
{%
set feature_community_feed = {
image_src: "/assets/images/activity-feed.png",
sections: [
{
title: "Community feed",
content: "Never miss an important mention, comment, pull request, or other
essential activity with Orbit's
Discourse, GitHub, and Twitter integrations."
},
{
title: "Automatic activity tracking",
content: "Connect directly to Discourse, GitHub, and Twitter, or use our API to automatically understand which developers are most active in your community."
}
]
}
%}
{{ single_feature_with_image(feature_community_feed) }}
{% include "newsletter-cta.njk" %}
{% include "for-devrels/view.njk" %}
{%
set feature_core_contributors = {
title: "Celebrate your core contributors",
image_src: "/assets/images/core-contributors.png",
sections: [
{
title: "We’ll keep an eye on things",
content: "Orbit will keep track of key moments across your community and
let you know when Members achieve important milestones. Never miss
a moment, and respond right from inside Orbit."
}
]
}
%}
{{ single_feature_with_image(feature_core_contributors) }}
{%
set feature_search_box = {
image_src: "/assets/images/devrel-search-box.png",
sections: [
{
title: "The unified search box for your community",
content: "Orbit search indexes and returns company names, locations, tags, notes,
and profile data like top languages, the names of repos contributed to,
and the content of relevant tweets."
}
]
}
%}
{%
set feature_identity_resolution = {
image_src: "/assets/images/devrel-identity-resolution.png",
sections: [
{
title: "Intelligent Identity Resolution",
content: "View side-by-side comparisons of potential duplicates, allowing you to quickly
clean your data. You’ll also see call-outs on individual profiles, alerting you
to potential conflicts as you navigate Orbit."
}
]
}
%}
{{ double_feature_with_images("Data tools that give you superpowers", feature_search_box, feature_identity_resolution) }}
{%
set feature_metrics_report = {
image_src: "/assets/images/devrel-metrics-1.png",
sections: [
{
title: "Report with confidence",
content: "Demonstrate the impact of your community investments with simple
and powerful reporting."
}
]
}
%}
{%
set feature_metrics_share = {
image_src: "/assets/images/devrel-metrics-2.png",
sections: [
{
title: "Share the success",
content: "Receive weekly reports about community engagement and top contributors.
Share and celebrate with your team."
}
]
}
%}
{{ double_feature_with_images("Metrics that matter", feature_metrics_report, feature_metrics_share, "sm:-mt-10") }}
{% include "ready-to-try-it.njk" %}


6 Changes in Search Engines You Need To Be On the Lookout For
by AJ Agrawal
How can advertisers and marketers fit in with the content and results retrieved by different search engines? Can we pinpoint these changes? What relevance do they have for us in the end?


Podcast Selection |
|
|---|---|
Select Podcast |
|
Navigate |
|
Jump to Top |
|
Jump to Bottom |
|
Page Up |
|
Page Down |
|
Toggle Fullscren |
|
Podcast Player |
|
Play/Pause |
|
Skip Back |
|
Skip Forward |
|
Skip Back |
|
Skip Forward |
|
Scrub Back |
|
Scrub Forward |
|
Delete Podcast |


LAMA.js is html5 and JS based web app developed by Praveen Manoharan. This can be used on phonegap or cordova projects and also use it as an simple web application. Still its under construction. Contribution to the code to add some new eature or improvement is welcome. Cheesee....


CVE-2022-41966: XStream is vulnerable to a Denial of Service attack due to stack overflow.
All versions until and including version 1.4.19 are affected, if using the version out of the box.
The processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a stack overflow calculating a recursive hash set causing a denial of service.
Create a simple HashSet and use XStream to marshal it to XML. Replace the XML with following snippet and unmarshal it with XStream:
<set> <set> <set> <set> <set> <set> <set> <string>a</string> </set> <set> <string>b</string> </set> </set> <set> <string>c</string> <set reference='../../../set/set[2]'/> </set> </set> </set> </set> </set> </set>
XStream xstream = new XStream(); xstream.fromXML(xml);
As soon as the XML gets unmarshalled, the recursive hash calculation is entered and the executing thread is aborted with a stack overflow error.
The vulnerability may allow a remote attacker to terminate the application with a stack overflow error resulting in a denial of service only by manipulating the processed input stream.
A simple solution is to catch the StackOverflowError in the client code calling XStream.
If your object graph does not use referenced elements at all, you may simply set the NO_REFERENCE mode:
XStream xstream = new XStream(); xstream.setMode(XStream.NO_REFERENCES);
If your object graph contains neither a Hashtable, HashMap nor a HashSet (or one of the linked variants of it) then you can use the security framework to deny the usage of these types:
XStream xstream = new XStream(); xstream.denyTypes(new Class[]{ java.util.HashMap.class, java.util.HashSet.class, java.util.Hashtable.class, java.util.LinkedHashMap.class, java.util.LinkedHashSet.class });
Unfortunately these types are very common. If you only use HashMap or HashSet and your XML refers these only as default map or set, you may additionally change the default implementation of java.util.Map and java.util.Set at unmarshalling time:
xstream.addDefaultImplementation(java.util.TreeMap.class, java.util.Map.class); xstream.addDefaultImplementation(java.util.TreeSet.class, java.util.Set.class);
However, this implies that your application does not care about the implementation of the map and all elements are comparable.
There is no known workaround to prevent this error except by catching the error in the code calling XStream.
Lai Han of nsfocus security team found and reported the issue to XStream and provided the required information to reproduce it.