1983 Football League Cup Final

The 1983 Football League Cup Final was a football match held on 26 March 1983 between League Cup holders Liverpool and first-time finalists Manchester United, who won the FA Cup later that year. Liverpool won the match 2–1; Norman Whiteside scored the opener for Manchester United, before Alan Kennedy equalised with 15 minutes to go. The winner was scored in the eighth minute of extra-time by Ronnie Whelan.

1983 Football League Cup Final
Event1982–83 Football League Cup
Liverpool Manchester United
2 1
After extra time
Date26 March 1983
VenueWembley Stadium, London
RefereeGeorge Courtney (County Durham)
Attendance99,304

Had Manchester United won the League Cup as well as the FA Cup that year, they would have become the first team ever to have won the two competitions in the same season. Instead, Liverpool won their third successive League Cup, and the second of three successive League and League Cup Doubles.

The match was played at Wembley Stadium in front of approximately 100,000 spectators.

Liverpool manager Bob Paisley collected the trophy, as it was his last major final in charge of Liverpool.

Match details
Liverpool2–1 (a.e.t.)Manchester United
Kennedy  75'
Whelan  98'		 Report Whiteside  12'
Attendance: 99,304
Liverpool
Manchester United
GK1 Bruce Grobbelaar
RB2 Phil Neal
LB3 Alan Kennedy
CB4 Mark Lawrenson
LM5 Ronnie Whelan
CB6 Alan Hansen
CF7 Kenny Dalglish
RM8 Sammy Lee
CF9 Ian Rush
CM10 Craig Johnston 83'
CM11 Graeme Souness (c)
Substitute:
FW12 David Fairclough 83'
Manager:
Bob Paisley
GK1 Gary Bailey
RB2 Mike Duxbury
LB3 Arthur Albiston
CM4 Remi Moses
CB5 Kevin Moran 69'
CB6 Gordon McQueen
CM7 Ray Wilkins (c)
LM8 Arnold Mühren
CF9 Frank Stapleton
CF10 Norman Whiteside
RM11 Steve Coppell
Substitute:
FW12 Lou Macari 69'
Manager:
Ron Atkinson

Match rules

  • 90 minutes.
  • 30 minutes of extra-time if necessary.
  • Replay if scores still level.
  • One named substitute.
  • Maximum of one substitution.
gollark: <@!206233133228490752> Sorry to bother you, but keypairs generated by `ccecc.py` and the ECC library in use in potatOS appear to have different-length private and public keys, which is a problem.EDIT: okay, apparently it's because I've been accidentally using a *different* ECC thing from SMT or something, and it has these parameters instead:```---- Elliptic Curve Arithmetic---- About the Curve Itself-- Field Size: 192 bits-- Field Modulus (p): 65533 * 2^176 + 3-- Equation: x^2 + y^2 = 1 + 108 * x^2 * y^2-- Parameters: Edwards Curve with c = 1, and d = 108-- Curve Order (n): 4 * 1569203598118192102418711808268118358122924911136798015831-- Cofactor (h): 4-- Generator Order (q): 1569203598118192102418711808268118358122924911136798015831---- About the Curve's Security-- Current best attack security: 94.822 bits (Pollard's Rho)-- Rho Security: log2(0.884 * sqrt(q)) = 94.822-- Transfer Security? Yes: p ~= q; k > 20-- Field Discriminant Security? Yes: t = 67602300638727286331433024168; s = 2^2; |D| = 5134296629560551493299993292204775496868940529592107064435 > 2^100-- Rigidity? A little, the parameters are somewhat small.-- XZ/YZ Ladder Security? No: Single coordinate ladders are insecure, so they can't be used.-- Small Subgroup Security? Yes: Secret keys are calculated modulo 4q.-- Invalid Curve Security? Yes: Any point to be multiplied is checked beforehand.-- Invalid Curve Twist Security? No: The curve is not protected against single coordinate ladder attacks, so don't use them.-- Completeness? Yes: The curve is an Edwards Curve with non-square d and square a, so the curve is complete.-- Indistinguishability? No: The curve does not support indistinguishability maps.```so I might just have to ship *two* versions to keep compatibility with old signatures.
gollark: > 2. precompilation to lua bytecode and compressionThis was considered, but the furthest I went was having some programs compressed on disk.
gollark: > 1. multiple layers of sandboxing (a "system" layer that implements a few things, a "features" layer that implements most of potatOS's inter-sandboxing API and some features, a "process manager" layer which has inter-process separation and ways for processes to communicate, and a "BIOS" layer that implements features like PotatoBIOS)Seems impractical, although it probably *could* fix a lot of problems
gollark: There's a list.
gollark: Lots of them.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.