Online Check-In for 2 Adults from Different Households/Countries

[Sarco11]

My friend (from Canada) and I are going on a 3-Night Dream cruise in mid-May and sharing a stateroom. I did my online check-in, but am trying to figure out the best way to get her required images uploaded in a secure way (no emailing or texting photos of her passport!)

She is part of my Friends & Family, but should she herself have her own Disney account?

I know that she will have to do her own Safe Passages account.

We were just planning to have a video conference during which I was going to guide her through logging into my Disney account on her device so that she can upload her documents. I guess that I also need to tell her to download the DCL app.

I am on hold, but would rather not have a hold of undefined length if someone on this forum has experience with this issue.

Thanks!

 

[Kwami]

1. As you said, you could have her log into your account and upload the information herself. You'll have to share your password, though. I guess a video conference might be better than plain text email, sure, but you might be better off with a regular phone call for sharing a password.

2. You could have her create a zip file that contains her photos and encrypt it. Most zip utilities have this feature. She would have to give you the password to decrypt it, of course. But, that would let her email you the documents.

Those are the two easiest ways that I thought of. They aren't great, but they're much better than just emailing passport photos!

Anyway, enjoy your cruise!

 

[Sarco11]

1. As you said, you could have her log into your account and upload the information herself. You'll have to share your password, though. I guess a video conference might be better than plain text email, sure, but you might be better off with a regular phone call for sharing a password.

2. You could have her create a zip file that contains her photos and encrypt it. Most zip utilities have this feature. She would have to give you the password to decrypt it, of course. But, that would let her email you the documents.

Those are the two easiest ways that I thought of. They aren't great, but they're much better than just emailing passport photos!

Anyway, enjoy your cruise!

Thanks! True, regular video conferencing is also not necessarily secure. I can wait 'til May 12th to see her face again A regular call should suffice.

I am kind of over this Disney hold music.

 

[YourEveryDayAdam]

at our office we use a service called SendSafely (sendsafely.com) to send stuff by email securely.

Basically, you upload your documents to it and type in the recipients email address, it generates a secure URL, you send the URL to the recipient by a method other than email (Facebook, IM, telegram, text, etc.). Send safely then validates they own the email address by emailing a 6 digit code to the email address.

Basically, the stuff you upload is encrypted on your browser, the web address contains the decryption key, sendsafely has no way to decrypt it themselves, and then if someone should intercept the web address sendsafely still validates that you are supposed to be able to open it by doing the email address validate.

You can open a free account with them and send 50mb of stuff per month.

I am not affiliated with them in any way. It's just what we use at our office to send stuff securely.

 

[Kwami]

at our office we use a service called SendSafely (sendsafely.com) to send stuff by email securely.

Basically, you upload your documents to it and type in the recipients email address, it generates a secure URL, you send the URL to the recipient by a method other than email (Facebook, IM, telegram, text, etc.). Send safely then validates they own the email address by emailing a 6 digit code to the email address.

Basically, the stuff you upload is encrypted on your browser, the web address contains the decryption key, sendsafely has no way to decrypt it themselves, and then if someone should intercept the web address sendsafely still validates that you are supposed to be able to open it by doing the email address validate.

You can open a free account with them and send 50mb of stuff per month.

I am not affiliated with them in any way. It's just what we use at our office to send stuff securely.

That can't be how it works. If the "web address" contains the decryption key, then SendSafely absolutely could decrypt the files. Or anyone else with the address, really.

 

[auntlynne]

Have her create her own Disney account, as you suggested. Why jump through extra hoops?

She’ll probably need it to use the app once onboard.

 

[Kwami]

Have her create her own Disney account, as you suggested. Why jump through extra hoops?

She’ll probably need it to use the app once onboard.

You don't need an account to use the app onboard. You log in with your name and room number.

 

[auntlynne]

You don't need an account to use the app onboard. You log in with your name and room number.

I’ll tuck that info in my hat. Can you use it pre-Cruise with that info, too? (Everyone in my family, all adults, manages their own info; so, asking for future readers). Thank you.

 

[Kwami]

I’ll tuck that info in my hat. Can you use it pre-Cruise with that info, too? (Everyone in my family, all adults, manages their own info; so, asking for future readers). Thank you.

No. Before the cruise, you need an account. The app is completely different once your connect to the DCL-Guest WiFi network.

 

[YourEveryDayAdam]

That can't be how it works. If the "web address" contains the decryption key, then SendSafely absolutely could decrypt the files. Or anyone else with the address, really.

The portion of the web address is contained in a section that doesn't get transmitted to sendsafely. This is a bit technical, and I won't go over the specifics, but here is an example:

https://www.sendsafely.com/receive/?thread=3XXW‑79TN&packageCode=9TH2l0FzSKIPZB0Wo4GkuGOs0WGagTB4EQzNEb1raFA#keyCode=2sUgGaPh475QZ5F4WHOLteJ0eIsbVq2HEn7Ja6PA_Vk

Everything after the "#" in a web address is called the "fragment" and it doesn't gets sent to the server. So This portion is never sent to send safely: #keyCode=2sUgGaPh475QZ5F4WHOLteJ0eIsbVq2HEn7Ja6PA_Vk

However, it's available to your browser. This basically means that sendsafely never sees the key to decrypt. But it is available for your web browser to use to decrypt the data.

from wikiepedia: https://en.wikipedia.org/wiki/URI_fragment#:~:text=The fragment identifier introduced by,is specified in RFC 3986.
"Clients are not supposed to send URI fragments to servers when they retrieve a document"

 

[Kwami]

Ah, fair enough. That's a neat way to do it.