La auditoría preliminar sobre la reciente intrusión en los sistemas de la autoridad certificadora DigiNotar puso de manifiesto cómo el descuido de políticas de seguridad básicas dio lugar a una intrusión de tal dimensión. Falta de antivirus, contraseñas débiles, servidores CA dentro de un mismo dominio, software desactualizado, carencia de sistemas de validación de credenciales (login), etc. presentan el caldo de cultivo perfecto para un A.P.T (Advance Persistent Threat).
Via: Cert INTECO Gathering
21 nov 2011
10 nov 2011
Oracle Distributed Recovery process
The RECO background process (Distributed Recovery process) of an Oracle instance
automatically resolves failures involving distributed transactions, when the
machine, network, or software problem is resolved.
Until RECO can resolve the transaction, the data is locked for both reads and writes.
Oracle blocks reads because it cannot
determine which version of the data to display for a query.
determine which version of the data to display for a query.
3 nov 2011
Oracle Backgroung Process !!!
Muy importante para tener en cuenta... :p
Never have a script which would kill any background processes, in which case it can have harmful effects on the database."
With most background processes (ie., RECO, ARCH, PMON), if they encounter failure or if are killed,
the database will crash and this is expected behavior.
Never have a script which would kill any background processes, in which case it can have harmful effects on the database."
With most background processes (ie., RECO, ARCH, PMON), if they encounter failure or if are killed,
the database will crash and this is expected behavior.
1 nov 2011
Oracle Recoverer Process (RECO)
Recoverer Process (RECO)
The recoverer process (RECO) is a background process used with the distributed database configuration that automatically resolves failures involving distributed transactions. The RECO process of a node automatically connects to other databases involved in an in-doubt distributed transaction. When the RECO process reestablishes a connection between involved database servers, it automatically resolves all in-doubt transactions, removing from each database's pending transaction table any rows that correspond to the resolved in-doubt transactions.
If the RECO process fails to connect with a remote server, RECO automatically tries to connect again after a timed interval. However, RECO waits an increasing amount of time (growing exponentially) before it attempts another connection. The RECO process is present only if the instance permits distributed transactions. The number of concurrent distributed transactions is not limited.
The recoverer process (RECO) is a background process used with the distributed database configuration that automatically resolves failures involving distributed transactions. The RECO process of a node automatically connects to other databases involved in an in-doubt distributed transaction. When the RECO process reestablishes a connection between involved database servers, it automatically resolves all in-doubt transactions, removing from each database's pending transaction table any rows that correspond to the resolved in-doubt transactions.
If the RECO process fails to connect with a remote server, RECO automatically tries to connect again after a timed interval. However, RECO waits an increasing amount of time (growing exponentially) before it attempts another connection. The RECO process is present only if the instance permits distributed transactions. The number of concurrent distributed transactions is not limited.
Suscribirse a:
Entradas (Atom)