How are SIGHASH flags encoded into a signature?

This page describes SIGHASH flags:

OP_CHECKSIG extracts a non-stack argument from each signature it evaluates, allowing the signer to decide which parts of the transaction to sign. Since the signature protects those parts of the transaction from modification, this lets signers selectively choose to let other people modify their transactions.

But how can I extract the SIGHASH flags from the signature?

Using Bitcore API for Escrow

Has anyone experience using the Bitcore API for Escrow purposes with node.js?

I assume, you’d need to create a new a address, then somehow create a new transaction using the newly created address, the probe that address for it’s balance until its fulfilled. I’ve had a look over the docs, but couldn’t find anything. Currently you can run bitcoind on a server and connect to this using RPC, but I’d like to try using Bitcore instead but achieve the same result.

Thanks.

About performing SHA-256 hashing on the public key

I am following this link, trying to perform SHA-256 on a given public key.
However, I cannot get the expected result.

I am using the sha256 library in python hashlib

The input is

0450863AD64A87AE8A2FE83C1AF1A8403CB53F53E486D8511DAD8A04887E5B23522CD470243453A299FA9E77237716103ABC11A1DF38855ED6F2EE187E9C582BA6

Mine output is

32511e82d56dcea68eb774094e25bab0f8bdd9bc1eca1ceeda38c7a43aceddce

The expected output on bitcoin.it is

600FFE422B4E00731A59557A5CCA46CC183944191006324A447BDB2D98D4B408

Do I miss anything?