public abstract class CipherSpi extends Object
Cipher
class.
All the abstract methods in this class must be implemented by each
cryptographic service provider who wishes to supply the implementation
of a particular cipher algorithm.
In order to create an instance of Cipher
, which
encapsulates an instance of this CipherSpi
class, an
application calls one of the
getInstance
factory methods of the
Cipher
engine class and specifies the requested
transformation.
Optionally, the application may also specify the name of a provider.
A transformation is a string that describes the operation (or set of operations) to be performed on the given input, to produce some output. A transformation always includes the name of a cryptographic algorithm (e.g., DES), and may be followed by a feedback mode and padding scheme.
A transformation is of the form:
(in the latter case, provider-specific default values for the mode and padding scheme are used). For example, the following is a valid transformation:
Cipher c = Cipher.getInstance("DES/CBC/PKCS5Padding");
A provider may supply a separate class for each combination
of algorithm/mode/padding, or may decide to provide more generic
classes representing sub-transformations corresponding to
algorithm or algorithm/mode or algorithm//padding
(note the double slashes),
in which case the requested mode and/or padding are set automatically by
the getInstance
methods of Cipher
, which invoke
the engineSetMode
and
engineSetPadding
methods of the provider's subclass of CipherSpi
.
A Cipher
property in a provider master class may have one of
the following formats:
// provider's subclass of "CipherSpi" implements "algName" with
// pluggable mode and padding
Cipher.
algName
// provider's subclass of "CipherSpi" implements "algName" in the
// specified "mode", with pluggable padding
Cipher.
algName/mode
// provider's subclass of "CipherSpi" implements "algName" with the
// specified "padding", with pluggable mode
Cipher.
algName//padding
// provider's subclass of "CipherSpi" implements "algName" with the
// specified "mode" and "padding"
Cipher.
algName/mode/padding
For example, a provider may supply a subclass of CipherSpi
that implements DES/ECB/PKCS5Padding, one that implements
DES/CBC/PKCS5Padding, one that implements
DES/CFB/PKCS5Padding, and yet another one that implements
DES/OFB/PKCS5Padding. That provider would have the following
Cipher
properties in its master class:
Cipher.
DES/ECB/PKCS5Padding
Cipher.
DES/CBC/PKCS5Padding
Cipher.
DES/CFB/PKCS5Padding
Cipher.
DES/OFB/PKCS5Padding
Another provider may implement a class for each of the above modes
(i.e., one class for ECB, one for CBC, one for CFB,
and one for OFB), one class for PKCS5Padding,
and a generic DES class that subclasses from CipherSpi
.
That provider would have the following
Cipher
properties in its master class:
Cipher.
DES
The getInstance
factory method of the Cipher
engine class follows these rules in order to instantiate a provider's
implementation of CipherSpi
for a
transformation of the form "algorithm":
CipherSpi
for the specified "algorithm".
If the answer is YES, instantiate this class, for whose mode and padding scheme default values (as supplied by the provider) are used.
If the answer is NO, throw a NoSuchAlgorithmException
exception.
The getInstance
factory method of the Cipher
engine class follows these rules in order to instantiate a provider's
implementation of CipherSpi
for a
transformation of the form "algorithm/mode/padding":
CipherSpi
for the specified "algorithm/mode/padding" transformation.
If the answer is YES, instantiate it.
If the answer is NO, go to the next step.
CipherSpi
for the sub-transformation "algorithm/mode".
If the answer is YES, instantiate it, and call
engineSetPadding(padding)
on the new instance.
If the answer is NO, go to the next step.
CipherSpi
for the sub-transformation "algorithm//padding" (note the double
slashes).
If the answer is YES, instantiate it, and call
engineSetMode(mode)
on the new instance.
If the answer is NO, go to the next step.
CipherSpi
for the sub-transformation "algorithm".
If the answer is YES, instantiate it, and call
engineSetMode(mode)
and
engineSetPadding(padding)
on the new instance.
If the answer is NO, throw a NoSuchAlgorithmException
exception.
KeyGenerator
,
SecretKey
| Constructor and Description |
|---|
CipherSpi() |
| Modifier and Type | Method and Description |
|---|---|
protected abstract byte[] |
engineDoFinal(byte[] input,
int inputOffset,
int inputLen)
Encrypts or decrypts data in a single-part operation,
or finishes a multiple-part operation.
|
protected abstract int |
engineDoFinal(byte[] input,
int inputOffset,
int inputLen,
byte[] output,
int outputOffset)
Encrypts or decrypts data in a single-part operation,
or finishes a multiple-part operation.
|
protected int |
engineDoFinal(ByteBuffer input,
ByteBuffer output)
Encrypts or decrypts data in a single-part operation,
or finishes a multiple-part operation.
|
protected abstract int |
engineGetBlockSize()
Returns the block size (in bytes).
|
protected abstract byte[] |
engineGetIV()
Returns the initialization vector (IV) in a new buffer.
|
protected int |
engineGetKeySize(Key key)
Returns the key size of the given key object in bits.
|
protected abstract int |
engineGetOutputSize(int inputLen)
Returns the length in bytes that an output buffer would
need to be in order to hold the result of the next
update
or doFinal operation, given the input length
inputLen (in bytes). |
protected abstract AlgorithmParameters |
engineGetParameters()
Returns the parameters used with this cipher.
|
protected abstract void |
engineInit(int opmode,
Key key,
AlgorithmParameterSpec params,
SecureRandom random)
Initializes this cipher with a key, a set of
algorithm parameters, and a source of randomness.
|
protected abstract void |
engineInit(int opmode,
Key key,
AlgorithmParameters params,
SecureRandom random)
Initializes this cipher with a key, a set of
algorithm parameters, and a source of randomness.
|
protected abstract void |
engineInit(int opmode,
Key key,
SecureRandom random)
Initializes this cipher with a key and a source
of randomness.
|
protected abstract void |
engineSetMode(String mode)
Sets the mode of this cipher.
|
protected abstract void |
engineSetPadding(String padding)
Sets the padding mechanism of this cipher.
|
protected Key |
engineUnwrap(byte[] wrappedKey,
String wrappedKeyAlgorithm,
int wrappedKeyType)
Unwrap a previously wrapped key.
|
protected abstract byte[] |
engineUpdate(byte[] input,
int inputOffset,
int inputLen)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
protected abstract int |
engineUpdate(byte[] input,
int inputOffset,
int inputLen,
byte[] output,
int outputOffset)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
protected int |
engineUpdate(ByteBuffer input,
ByteBuffer output)
Continues a multiple-part encryption or decryption operation
(depending on how this cipher was initialized), processing another data
part.
|
protected void |
engineUpdateAAD(byte[] src,
int offset,
int len)
Continues a multi-part update of the Additional Authentication
Data (AAD), using a subset of the provided buffer.
|
protected void |
engineUpdateAAD(ByteBuffer src)
Continues a multi-part update of the Additional Authentication
Data (AAD).
|
protected byte[] |
engineWrap(Key key)
Wrap a key.
|
protected abstract void engineSetMode(String mode) throws NoSuchAlgorithmException
mode
- the cipher modeNoSuchAlgorithmException
- if the requested cipher mode does
not existprotected abstract void engineSetPadding(String padding) throws NoSuchPaddingException
padding
- the padding mechanismNoSuchPaddingException
- if the requested padding mechanism
does not existprotected abstract int engineGetBlockSize()
protected abstract int engineGetOutputSize(int inputLen)
update
or doFinal
operation, given the input length
inputLen
(in bytes).
This call takes into account any unprocessed (buffered) data from a
previous update
call, padding, and AEAD tagging.
The actual output length of the next update
or
doFinal
call may be smaller than the length returned by
this method.
inputLen
- the input length (in bytes)protected abstract byte[] engineGetIV()
This is useful in the context of password-based encryption or decryption, where the IV is derived from a user-provided passphrase.
protected abstract AlgorithmParameters engineGetParameters()
The returned parameters may be the same that were used to initialize this cipher, or may contain a combination of default and random parameter values used by the underlying cipher implementation if this cipher requires algorithm parameters but was not initialized with any.
protected abstract void engineInit(int opmode, Key key, SecureRandom random) throws InvalidKeyException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending on
the value of opmode
.
If this cipher requires any algorithm parameters that cannot be
derived from the given key
, the underlying cipher
implementation is supposed to generate the required parameters itself
(using provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidKeyException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
engineGetParameters
or
engineGetIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of
the following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipher, or requires
algorithm parameters that cannot be
determined from the given key.protected abstract void engineInit(int opmode, Key key, AlgorithmParameterSpec params, SecureRandom random) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending on
the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
engineGetParameters
or
engineGetIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of
the following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipherInvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or if this cipher requires
algorithm parameters and params
is null.protected abstract void engineInit(int opmode, Key key, AlgorithmParameters params, SecureRandom random) throws InvalidKeyException, InvalidAlgorithmParameterException
The cipher is initialized for one of the following four operations:
encryption, decryption, key wrapping or key unwrapping, depending on
the value of opmode
.
If this cipher requires any algorithm parameters and
params
is null, the underlying cipher implementation is
supposed to generate the required parameters itself (using
provider-specific default or random values) if it is being
initialized for encryption or key wrapping, and raise an
InvalidAlgorithmParameterException
if it is being
initialized for decryption or key unwrapping.
The generated parameters can be retrieved using
engineGetParameters
or
engineGetIV
(if the parameter is an IV).
If this cipher requires algorithm parameters that cannot be derived from the input parameters, and there are no reasonable provider-specific default values, initialization will necessarily fail.
If this cipher (including its underlying feedback or padding scheme)
requires any random bytes (e.g., for parameter generation), it will get
them from random
.
Note that when a Cipher object is initialized, it loses all previously-acquired state. In other words, initializing a Cipher is equivalent to creating a new instance of that Cipher and initializing it.
opmode
- the operation mode of this cipher (this is one of
the following:
ENCRYPT_MODE
, DECRYPT_MODE
,
WRAP_MODE
or UNWRAP_MODE
)key
- the encryption keyparams
- the algorithm parametersrandom
- the source of randomnessInvalidKeyException
- if the given key is inappropriate for
initializing this cipherInvalidAlgorithmParameterException
- if the given algorithm
parameters are inappropriate for this cipher,
or if this cipher requires
algorithm parameters and params
is null.protected abstract byte[] engineUpdate(byte[] input, int inputOffset, int inputLen)
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, are processed,
and the result is stored in a new buffer.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthprotected abstract int engineUpdate(byte[] input, int inputOffset, int inputLen, byte[] output, int outputOffset) throws ShortBufferException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, are processed,
and the result is stored in the output
buffer, starting at
outputOffset
inclusive.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutputOffset
- the offset in output
where the result
is storedoutput
ShortBufferException
- if the given output buffer is too small
to hold the resultprotected int engineUpdate(ByteBuffer input, ByteBuffer output) throws ShortBufferException
All input.remaining()
bytes starting at
input.position()
are processed. The result is stored
in the output buffer.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed. The output buffer's
position will have advanced by n, where n is the value returned
by this method; the output buffer's limit will not have changed.
If output.remaining()
bytes are insufficient to
hold the result, a ShortBufferException
is thrown.
Subclasses should consider overriding this method if they can process ByteBuffers more efficiently than byte arrays.
input
- the input ByteBufferoutput
- the output ByteByfferoutput
ShortBufferException
- if there is insufficient space in the
output bufferNullPointerException
- if either parameter is null
protected abstract byte[] engineDoFinal(byte[] input, int inputOffset, int inputLen) throws IllegalBlockSizeException, BadPaddingException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, and any input
bytes that may have been buffered during a previous update
operation, are processed, with padding (if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in a new buffer.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to
engineInit
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
engineInit
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthIllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.BadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valueprotected abstract int engineDoFinal(byte[] input, int inputOffset, int inputLen, byte[] output, int outputOffset) throws ShortBufferException, IllegalBlockSizeException, BadPaddingException
The first inputLen
bytes in the input
buffer, starting at inputOffset
inclusive, and any input
bytes that may have been buffered during a previous update
operation, are processed, with padding (if requested) being applied.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output
buffer, starting at
outputOffset
inclusive.
If the output
buffer is too small to hold the result,
a ShortBufferException
is thrown.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to
engineInit
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
engineInit
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
input
- the input bufferinputOffset
- the offset in input
where the input
startsinputLen
- the input lengthoutput
- the buffer for the resultoutputOffset
- the offset in output
where the result
is storedoutput
IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if the given output buffer is too small
to hold the resultBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valueprotected int engineDoFinal(ByteBuffer input, ByteBuffer output) throws ShortBufferException, IllegalBlockSizeException, BadPaddingException
All input.remaining()
bytes starting at
input.position()
are processed.
If an AEAD mode such as GCM/CCM is being used, the authentication
tag is appended in the case of encryption, or verified in the
case of decryption.
The result is stored in the output buffer.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed. The output buffer's
position will have advanced by n, where n is the value returned
by this method; the output buffer's limit will not have changed.
If output.remaining()
bytes are insufficient to
hold the result, a ShortBufferException
is thrown.
Upon finishing, this method resets this cipher object to the state
it was in when previously initialized via a call to
engineInit
.
That is, the object is reset and available to encrypt or decrypt
(depending on the operation mode that was specified in the call to
engineInit
) more data.
Note: if any exception is thrown, this cipher object may need to be reset before it can be used again.
Subclasses should consider overriding this method if they can process ByteBuffers more efficiently than byte arrays.
input
- the input ByteBufferoutput
- the output ByteByfferoutput
IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested (only in encryption mode), and the total
input length of the data processed by this cipher is not a multiple of
block size; or if this encryption algorithm is unable to
process the input data provided.ShortBufferException
- if there is insufficient space in the
output bufferBadPaddingException
- if this cipher is in decryption mode,
and (un)padding has been requested, but the decrypted data is not
bounded by the appropriate padding bytesAEADBadTagException
- if this cipher is decrypting in an
AEAD mode (such as GCM/CCM), and the received authentication tag
does not match the calculated valueNullPointerException
- if either parameter is null
protected byte[] engineWrap(Key key) throws IllegalBlockSizeException, InvalidKeyException
This concrete method has been added to this previously-defined abstract class. (For backwards compatibility, it cannot be abstract.) It may be overridden by a provider to wrap a key. Such an override is expected to throw an IllegalBlockSizeException or InvalidKeyException (under the specified circumstances), if the given key cannot be wrapped. If this method is not overridden, it always throws an UnsupportedOperationException.
key
- the key to be wrapped.IllegalBlockSizeException
- if this cipher is a block cipher,
no padding has been requested, and the length of the encoding of the
key to be wrapped is not a multiple of the block size.InvalidKeyException
- if it is impossible or unsafe to
wrap the key with this cipher (e.g., a hardware protected key is
being passed to a software-only cipher).protected Key engineUnwrap(byte[] wrappedKey, String wrappedKeyAlgorithm, int wrappedKeyType) throws InvalidKeyException, NoSuchAlgorithmException
This concrete method has been added to this previously-defined abstract class. (For backwards compatibility, it cannot be abstract.) It may be overridden by a provider to unwrap a previously wrapped key. Such an override is expected to throw an InvalidKeyException if the given wrapped key cannot be unwrapped. If this method is not overridden, it always throws an UnsupportedOperationException.
wrappedKey
- the key to be unwrapped.wrappedKeyAlgorithm
- the algorithm associated with the wrapped
key.wrappedKeyType
- the type of the wrapped key. This is one of
SECRET_KEY
, PRIVATE_KEY
, or
PUBLIC_KEY
.NoSuchAlgorithmException
- if no installed providers
can create keys of type wrappedKeyType
for the
wrappedKeyAlgorithm
.InvalidKeyException
- if wrappedKey
does not
represent a wrapped key of type wrappedKeyType
for
the wrappedKeyAlgorithm
.protected int engineGetKeySize(Key key) throws InvalidKeyException
This concrete method has been added to this previously-defined
abstract class. It throws an UnsupportedOperationException
if it is not overridden by the provider.
key
- the key object.InvalidKeyException
- if key
is invalid.protected void engineUpdateAAD(byte[] src, int offset, int len)
Calls to this method provide AAD to the cipher when operating in
modes such as AEAD (GCM/CCM). If this cipher is operating in
either GCM or CCM mode, all AAD must be supplied before beginning
operations on the ciphertext (via the update
and doFinal
methods).
src
- the buffer containing the AADoffset
- the offset in src
where the AAD input startslen
- the number of AAD bytesIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized), does not accept AAD, or if
operating in either GCM or CCM mode and one of the update
methods has already been called for the active
encryption/decryption operationUnsupportedOperationException
- if this method
has not been overridden by an implementationprotected void engineUpdateAAD(ByteBuffer src)
Calls to this method provide AAD to the cipher when operating in
modes such as AEAD (GCM/CCM). If this cipher is operating in
either GCM or CCM mode, all AAD must be supplied before beginning
operations on the ciphertext (via the update
and doFinal
methods).
All src.remaining()
bytes starting at
src.position()
are processed.
Upon return, the input buffer's position will be equal
to its limit; its limit will not have changed.
src
- the buffer containing the AADIllegalStateException
- if this cipher is in a wrong state
(e.g., has not been initialized), does not accept AAD, or if
operating in either GCM or CCM mode and one of the update
methods has already been called for the active
encryption/decryption operationUnsupportedOperationException
- if this method
has not been overridden by an implementation Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.


BEFORE THE NATIONAL GREEN TRIBUNAL CENTRAL ZONAL BENCH BHOPAL Original Application No. 28/2014 (CZ) CORAM: Hon'ble Mr. Justice Dalip Singh (Judicial Member) Hon'ble Mr. P.S. Rao (Expert Member) BETWEEN: Neeraj Chourasiya S/o Shri H.N.Chourasiya R/o House No. 144/1, Veer Sawarkar Marg, District Vidisha, (MP). ...... Applicant Versus 1. State of MP Through Principal Secretary Ministry of Urban Administration & Development Deptt. Vallabh Bhawan, Bhopal. 2. The Principal Secretary Ministry of Housing & Environment Deptt., Vallabh Bhawan, Bhopal. 3. Madhya Pradesh State Pollution Control Board, Through Member Secretary, E-5, Paryawaran Parisar, Arera Colony, Bhopal (MP). 4. District Collector, District Vidisha, MP 5. Chief Municipal Officer, Nagar Palika Parishad, District Vidisha, MP 6. M/s Satya Sai Agro Oils (Pvt.) Ltd. Through Managing Director, Sanchi Road, District Vidisha (MP) - 464001. ........ Respondents
Counsel for Applicant : Mr. Vijay Shahni, Advocate Counsel for Respondent No. 1,2&4 : Mr. Sachin K. Verma, Advocate Counsel for Respondent No. 3: Ms. Parul Bhadoria, Adv. for Shri Purushaindra Kaurav, Adv.
Shri P.S.Bundela, OIC Counsel for Respondent No. 5 : Shri Om S.Shrivastav, Advocate Counsel for Respondent No. 6 : Shri Rohit Saboo, Advocate Dated : August 11th, 2014 Delivered in Open Court by Hon'ble Mr. Justice Dalip Singh, Judicial Member
1. Reply of the Respondent No.5 has been filed today. The same is ordered to be taken on record. Copy of the reply has been furnished to the Applicant.
2. We have considered the submissions of the Learned Counsel for the Applicant as well as the reply filed on behalf of the Municipal Council, Vidisha, the MP State Pollution Control Board and Respondent No. 6, M/s Satya Sai Agro Oils (Pvt.) Ltd. The State Government has adopted the reply filed by the MP State Pollution Control Board.
3. On 05.07.2014, this Tribunal, hearing the parties, had noted the concern of the Applicant which primarily is regarding the storm water drain being constructed by the Municipal Council Vidisha in accordance with the Detailed Project Report (DPR) prepared by it and approved by the State Government. It was submitted and recorded by this Tribunal that there is a likelihood that the storm water drain would be mis-utilised for carrying untreated sewage water upstream of the river Betwa which would cause serious health hazard since the drinking water supply (Water Works) site is located downstream of the point where the storm water drain is being constructed and is going to enter the river Betwa. It was Page 2 submitted by the Applicant that the aforesaid storm water drain is constructed by the Municipal Council as per the DPR and plan prepared by it but it has not taken note of establishment of any sewage treatment plant and therefore would allow untreated sewage to enter upstream of the river and there being no means for taking such inflow up to the point of water works from where the drinking water supply would be made to the citizens of Vidisha, there is a likelihood of serious health hazard by consuming such polluted water.
4. We have perused the reply submitted by the MP State Pollution Control Board. The MPPCB has, so far as the factual position is concerned, accepted the fact that the storm water drain, to some extent, may carry untreated sewage and as per the present DPR, there is no provision for construction of any sewage treatment plant for checking untreated water including the sewage from entering the river Betwa as the existing sewage treatment plant is on the other side of the river which would not be of any use so far as the present storm water drain, under construction, is concerned.
5. This factual position is not in dispute and it is also not disputed that the above concern of the Applicant has not been taken into account while preparing the DPR for the construction of storm water drain as per the existing DPR. Therefore, we are of the view that the project would require the reconsideration and re-examination so as to seek the opinion of the MPPCB regarding the apprehensions which have been raised by the Applicant more particularly of allowing inflow of untreated sewage into the storm water drain and thereby enter into the river Betwa upstream the site of the water supply for the city of Vidisha.
Page 3
6. It was given out that while the construction work has commenced in accordance with the work order that has been issued for the construction of storm water drain, however, due to onset of the monsoon presently the work has been stopped and only about 15% of the work has been completed so far.
7. From the reply of the MPPCB also we would find that provisions with regard to the Water (Prevention and Control of Pollution) Act, 1974 and more particularly provisions contained under Section 24, 25 and 26 are required to be looked into as also the requirement for setting up of the sewage treatment plant in the present case at the suitable point alongwith the storm water drain to prevent untreated sewage from entering the river Betwa at the upstream point before the drinking water is drawn from the river.
8. We would accordingly direct that the Municipal Council Vidisha/Respondent No. 5 shall resubmit its DPR to the Regional Office of the MPPCB at Bhopal and the MPPCB shall within four weeks examine the same with their suggestion in consultation with the Municipal Council for checking the inflow of untreated sewage into the storm water drain and thereby into the river and also setting up of sewage treatment plant at a proper location.
9. Since this requirement was necessarily to have been taken care of in the beginning itself, while finalising the DPR, and before the work was actually commenced, we would further direct that any additional cost/funds that may be required by the Municipal Council shall be made available by the State Government in this behalf so that the project is completed within a reasonable time frame without delay.
Page 4
10. Within four weeks, the MPPCB shall examine the matter with their suggestions and forward the same to the Municipal Council which in turn shall approach the State for any necessary approval including financial sanctions in this behalf.
11. As regards the complaint of the Applicant with regard to Respondent No. 6 is concerned, we find from the reply of the MPPCB, in Para No. 8 the aforesaid Respondent Industry, M/s Satya Sai Agro Oils (Pvt.) Ltd. has applied for the necessary consent and has got valid consent both under both the Water and Air Acts. It was also submitted that continuous monitoring of the water and air samples at the site is being taken up and even the last inspection carried out on 21.03.2013 and 16.05.2014 do not show pollutants beyond the permissible limits. It was also submitted that necessary safeguards with regard to measures which are required to be taken under the Water Act and Air Act have been taken and equipment installed by the Respondent No. 6.
12. In view of the aforesaid, we would only direct that regular monitoring of the site and discharge from the plant of the Respondent No. 6 shall be carried out and Respondent No. 6 shall also take all necessary steps which are required for the operation of the said mechanism so that no effluent discharge without being treated is allowed to pollute the water as apprehended by the Applicant. We may also note that it was submitted by Respondent No. 6 that for augmenting their requirement of water at the plant they will also take suitable measures for utilisation of grey water after the same has been treated at the ETP so as to reduce the drawing up of the ground water and consumption of fresh water.
Page 5
13. It is also submitted that the Respondent No. 6 shall be undertaking extensive plantation programme within their premises in consultation with the MPPCB and complete within four weeks. The Respondent No. 6 also undertakes that they would submit their Corporate Social Responsibility (CSR) Plan to the Regional Office, MPPCB and take up works for the same in consultation with the MPPCB as well as the Municipal Council, Vidisha.
14. Having said so, we would give liberty to the Applicant that in case the Applicant at any point of time feels aggrieved by any action on the part of the Respondent No. 6, the Applicant would be free to approach the Tribunal in this matter.
15. One of the issues which have been raised in the petition and for which relief has been sought by the Applicant pertains to the encroachment by the Brick Kilns owners manufacturing bricks along the banks of river Betwa which is not only an encroachment but also having an adverse effect so far as the river and quality of water is concerned. We would accordingly direct the Respondent No. 4, District Collector, Vidisha to have the entire area inspected, monitor and remove all the encroachments and ensure that no unauthorised brick kiln is allowed to operate along the river Betwa and also ensure that in case there are any licences granted to such brick kilns, the terms and conditions of such licence are complied with. Such of the brick kilns which are unauthorised or do not have any valid licence shall be removed forthwith.
16. With the aforesaid directions, this O.A.No. 28/2014 stands disposed of.
No order as to costs.
Page 6
17. The matter shall be listed for reporting compliance on 12th November, 2014.
(Mr. Justice Dalip Singh) Judicial Member (Mr. P.S.Rao) Expert Member Bhopal:
August 11th, 2014 Page 7


{% import 'molecules.html' as molecules %} {% import 'atoms.html' as atoms %} {% macro list_of_images_and_heading(view) -%}


Plan to give derelict Dumbarton waterworks a new lease of life refused
Neighbours have raised concerns over antisocial behaviour at Garshake Waterworks.
by Lorraine WeirProposals to give the former Garshake Waterworks site a new lease of life having lain empty for the past 12 years have been refused.
Neighbours have expressed concern that the area has suffered from antisocial behaviour since the business owner took charge of the site.
Mr Lenny Donnelly, who operates LWS Engineering in Helensburgh, has outgrown his premises and planned to move to the land at the top of Garshake Road in Dumbarton for his Land Rover repair yard.
However, he has already been storing some vehicles at the site which objectors say has attracted bother.
West Dunbartonshire Council's planning committee refused the application yesterday (Wednesday).
A report which went to councillors read: “Since acquiring the site, the applicant has failed to secure it and antisocial activity has increased since they have occupied the site.”
Worries were also put forward by objectors about environmental concerns with one saying: “Fires have been started and the black toxic smoke emanating from this has a significant impact for residents in the area.”
Planning officers, however, recommended the application was granted saying it will result in the “regeneration and partial redevelopment of the area”.
Objections raised about the fact that it is against planning policy to allow such a development within the area are addressed by planners who state: “Whilst the proposed specialist vehicle repair business is not fully supported by greenbelt policies, it is considered a departure from these policies can be justified as the land constitutes a vacant and derelict brownfield site.”


This is a great place to introduce your company or project and describe what you do.
Vanessa's Cafe has been keeping up with the evolving standards of coffee drinking. From the infamous kapeng barako and also came up with delectable beverages and equally tempting pastries and savory dishes.
Every minute spent in our coffee shops is intended to weave rewarding experiences while enjoying our CDL products. Let our proficient baristas and accommodating staff provide you the kind of service that is bound to make you feel important.


Radio - Script Only
Do your own radio but let Asset writh the script. Let Asset tell your great story
Radio spots can be announcer read only or can be produced with music, talent etc. Lengths of 15 seconds, 30 seconds or 60 seconds. Spots can be produced as part of a series or as stand alones.
Develop script copy for 30 second ad.*
*Doesn't include hard costs.


This is an open-source project aiming to provide a free sudoku game to
play from your browser.
If your browser is compatible, it will display the Sudoku grid here
momentarily. If nothing happen, check if you are using an up-to-date
navigator or raise an issue.


Wrote this before, but a barber and a customer represent HMTL and CSS well. That being the customer is the HTML, providing the content with the hair they walked in with, and the barber being the CSS which provides the style for that hair.
Control Flow is the order in which the computer executes the code. Loops are code that just loop until the desired outcome executes, where the loop stops. An example for control flow is just plain instructions. We may be given a set of instructions that we must complete in order from what we were first told to the last thing that was said, and we just go about it. For loops, an example that I can think of is how we try to work on a task. Some people like to try to solve it, take a break, re-evaluate, then repeat, and end up getting no where, sometimes. But, when it works out, we get our desired result, which ends the loop until we get stuck again and then the cycle continues.
Dom = Document objecy model. The DOM is a browsers internal projection of a webpage. It can be munipulated using such tools as the in-built dev tools on chrome for example but also by languages such as javascript. The DOM is often seen as a "hierarchical structure" made up of different Nodes in a format being easy to understand for the browser. Nodes are everything that make up a website from elements to text conent to everything else; They are the objects. Above is an example of how the DOM is viewed and represents that each branch is leading to a child Node from a parent Node = "hierarchy structure" "Family-tree structure" etc.
Arrays hold information or values which are the same type, where as objects contain information on objects with different properties. Both can be accessed similarly with [] bracket notations for example, except Arrays use Index numbers because of where/what number the information is stored in that array. While objects use the property that we have used.
Functions are a block of statements that perform a task. This is useful because if/when we want to execute a bunch of statements many times, we can just call the function which will runs those same set of statements till you get your desired result.


var util = require('util');
var stream = require('stream');
// via http://www.bennadel.com/blog/2681-turning-buffers-into-readable-streams-in-node-js.htm
function BufferStream(source) {
Iif (!Buffer.isBuffer(source)) {
throw(new Error('Source must be a buffer.'));
}
// super constructor.
stream.Readable.call(this);
this._source = source;
// keep track of which portion of the source buffer is currently being pushed
// onto the internal stream buffer during read actions.
this._offset = 0;
this._length = source.length;
// when the stream has ended, try to clean up the memory references.
this.on('end', this._destroy);
}
util.inherits(BufferStream, stream.Readable);
// attempt to clean up variable references once the stream has been ended.
BufferStream.prototype._destroy = function () {
this._source = null;
this._offset = null;
this._length = null;
};
// read chunks from the source buffer into the underlying stream buffer.
BufferStream.prototype._read = function (size) {
// If we haven't reached the end of the source buffer, push the next chunk onto
// the internal stream buffer.
Eif (this._offset < this._length) {
this.push(this._source.slice(this._offset, (this._offset + size)));
this._offset += size;
}
// we've consumed the entire source buffer, close the readable stream.
Eif (this._offset >= this._length) {
this.push(null);
}
};
module.exports = BufferStream; |