Generally we discourage the use of the word "any" in a crypto ACL, but it should be all you need. At the remote site router (with network 10.1.1.0/24), you'll have a standard crypto ACL that looks like:
access-list 101 permit ip 10.1.1.0 0.0.0.255 any
Then on the hub router, again it'll be standard with the crypto ACL for this site looking like:
access-list 101 permit ip any 10.1.1.0 0.0.0.255
If you have NAT at the remote site, you can either turn it off altogether, since there's not much point having it, or do the standard nonat route-map pointing to an access-list that denies traffic from 10.1.1.0/24 to any (as I said though, not much point having it all though).