-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle file/directory collisions #3
Comments
@luminous8 you or whoever produced that WACZ should log out of Stripe; the capture contains session cookies. Sorry; I should have been more clear about asking for you to send it privately. |
Thanks for noticing! What's the best way to send you a Wacz file privately? |
I typically use Keybase for something like this (where I'm I think the service you used generates one-time links? If so, then just sending me a link via email is probably fine; you can be pretty well assured that if I downloaded it, no one else did. I occasionally use a DIY arrangement like this, flahspaper, which is my version of go-flashpaper. If the material is too sensitive to risk someone else downloading it, I'd find a more secure channel than email for conveying the one-time link, maybe Signal (after providing my Signal username via email). Sorry if that's more than you bargained for! I bet there are other reasonable options. |
Thanks @bensteinberg |
Thanks, got it, and nice timing -- I just sat down to look at this issue again. |
See #1 for another error; @luminous8 reports
and reports that
I wrote
The text was updated successfully, but these errors were encountered: