Add a separate handoff step
Share a LOCK.PUB URL in the main conversation and send the password through another channel before the recipient reaches Drive.
Paste a Google Drive or Google Docs sharing URL, set a separate password, and share the new LOCK.PUB link instead of the original URL.
LOCK.PUB controls access through the protected link you share. Google Drive permissions still control the file, and anyone who already has the original Drive URL can bypass this gate.
Share a LOCK.PUB URL in the main conversation and send the password through another channel before the recipient reaches Drive.
Keep the Drive sharing URL out of the message body and place it behind a password prompt instead.
Continue using restricted, organization-only, or anyone-with-the-link settings in Google Drive as appropriate for the file.
The two controls work at different layers: LOCK.PUB asks for a password before revealing the destination URL, while Google Drive decides what that URL can open.
Swipe horizontally to compare every column.
| Feature | LOCK.PUB-gated Drive link | Direct Drive sharing URL |
|---|---|---|
| Password before the Drive URL is revealed | Required | No separate password gate |
| Original Drive URL visible in the shared message | No | Yes |
| Google Drive sharing permissions | Still apply | Apply directly |
| Protects someone who already has the original URL | No | Not applicable |
| Encrypts or changes the Drive file | No | No |
No. LOCK.PUB adds a password gate before revealing the Drive sharing URL. It does not change or encrypt the file stored in Google Drive.
Yes. Anyone who already has the original destination URL can use it directly, so share the protected LOCK.PUB link instead and keep the original URL private.
Yes. The recipient must still satisfy the Drive file permissions after unlocking the destination. A LOCK.PUB password does not replace Drive access controls.
No. LOCK.PUB is an independent service that can place a password step in front of supported Google Drive and Google Docs sharing URLs.