Duke of Santángelo

Duke of Santángelo (Spanish: Duque de Santángelo) is a hereditary title in the Peerage of Spain, accompanied by the dignity of Grandee and granted in 1497 by the Catholic Monarchs to "El Gran Capitán" (Gonzalo Fernández de Córdoba), a general who negotiated the Surrender of Granada and led the Spanish to victory in the Italian Wars.[3] It is a victory title, making reference to the town of Città Sant'Angelo in the Province of Pescara, Italy.

Dukedom of Santángelo
Creation date10 March 1497
MonarchCatholic Monarchs
PeeragePeerage of Spain
First holderGonzalo Fernández de Córdoba y Enríquez de Aguilar, 1st Duke of Terranova
Present holderLuis María de Casanova-Cárdenas y Barón, 5th Duke of Santángelo[1]
Heir apparentBaltasar Carlos de Casanova-Cárdenas y Habsburgo-Lorena, former 12th Marquess of Elche[2]

The title became extinct after the death of the 3rd Duke in 1578 and was rehabilitated in 1918 by Alfonso XIII on behalf of María de la Soledad Osorio de Moscoso, the most legitimate descendant of the last Duke and a great-grandchild of Infanta Luisa Teresa of Spain.

The current Duke, Luis María de Casanova-Cárdenas, is married to Archduchess Monika of Austria (his fifth cousin once-removed), the second child of Otto von Habsburg, crown prince of Austria, and Princess Regina of Saxe-Meiningen. They have 4 children.

Dukes of Santángelo

  1. Gonzalo Fernández de Córdoba y Enríquez de Aguilar, 1st Duke of Santángelo
  2. Elvira Fernández de Córdoba y Manrique, 2nd Duchess of Santángelo
  3. Gonzalo Fernández de Córdoba y Fernández de Córdoba, 3rd Duke of Santángelo
  4. María de la Soledad Osorio de Moscoso y Reynoso, 4th Duchess of Santángelo
  5. Luis María de Casanova-Cárdenas y Barón, 5th Duke of Santángelo
gollark: > ah so add like a random delay before it returns, or something?... no, they could filter that out using magic, you need a constant time comparison thing.
gollark: Sorry, the two input hashes.
gollark: If they put in one thing, and observe that it takes slightly longer, then that implies that more of the characters in the ~~password~~ one secret value versus the other match at the start.
gollark: But consider: attackers may be able to measure minor differences in the timing of operations in your service.
gollark: > Also, just using == to compare ~~a password and hash~~ secret values of some kind is actually somewhat unsafe because timing channel attacks.To continue this, basically, `==`/string equality/whatever will generally exit early if it detects a character which doesn't match.

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.