Add support for crypto 1.0.0.

lib/src/web_socket/compatible.dart

 // Copyright (c) 2014, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 import 'dart:async';
+import 'dart:convert';
 
 import 'package:crypto/crypto.dart';
 
 import '../copy/web_socket_impl.dart';
 
 /// This class is deprecated.
 ///
 /// Use the [`web_socket_channel`][web_socket_channel] package instead.
 ///
 /// [web_socket_channel]: https://pub.dartlang.org/packages/web_socket_channel
@@ skipping 28 matching lines @@
   String get closeReason;
 
   /// Signs a `Sec-WebSocket-Key` header sent by a WebSocket client as part of
   /// the [initial handshake].
   ///
   /// The return value should be sent back to the client in a
   /// `Sec-WebSocket-Accept` header.
   ///
   /// [initial handshake]: https://tools.ietf.org/html/rfc6455#section-4.2.2
   static String signKey(String key) {
-    var hash = new SHA1();
     // We use [codeUnits] here rather than UTF-8-decoding the string because
     // [key] is expected to be base64 encoded, and so will be pure ASCII.
-    hash.add((key + webSocketGUID).codeUnits);
-    return CryptoUtils.bytesToBase64(hash.close());
+    return BASE64.encode(sha1.convert((key + webSocketGUID).codeUnits).bytes);
   }
 
   /// Creates a new WebSocket handling messaging across an existing socket.
   ///
   /// Because this is HTTP-API-agnostic, the initial [WebSocket handshake][]
   /// must have already been completed on the socket before this is called.
   ///
   /// If [stream] is also a [StreamSink] (for example, if it's a "dart:io"
   /// `Socket`), it will be used for both sending and receiving data. Otherwise,
   /// it will be used for receiving data and [sink] will be used for sending it.
@@ skipping 20 matching lines @@
   /// Closes the web socket connection.
   ///
   /// [closeCode] and [closeReason] are the [close code][] and [reason][] sent
   /// to the remote peer, respectively. If they are omitted, the peer will see
   /// a "no status received" code with no reason.
   ///
   /// [close code]: https://tools.ietf.org/html/rfc6455#section-7.1.5
   /// [reason]: https://tools.ietf.org/html/rfc6455#section-7.1.6
   Future close([int closeCode, String closeReason]);
 }