Possible to generate our own random token? #368

New Issue

michael · 2026-01-19T18:30:03Z

michael commented

2026-01-19 18:30:03 +00:00

Originally created by @chiwalfrm on GitHub.

I have one PC that needs to share a file that changes daily with another PC remotely (not on same network).

I looked at the example provided on the website:
(Uploading is easy using curl)
$ curl --upload-file ./hello.txt https://transfer.sh/hello.txt
https://transfer.sh/66nb8/hello.txt
(Download the file)
$ curl https://transfer.sh/66nb8/hello.txt -o hello.txt

After the upload, the curl command returns a URL with a random token ("66nb8" in the above example). The problem is the other PC doesn't know the random token, and also I want to put the download command in cron. Is it possible for us to specify our own random token that we could use over and over? The file is encrypted so security concern with plaintext URL is not a problem.

curl --upload-file ./hello.txt https://transfer.sh/3b2rd9n3kbew8jhs/hello.txt

...where 3b2rd9n3kbew8jhs is the random token chosen by the user.

Thank you.

Originally created by @chiwalfrm on GitHub. I have one PC that needs to share a file that changes daily with another PC remotely (not on same network). I looked at the example provided on the website: (Uploading is easy using curl) $ curl --upload-file ./hello.txt https://transfer.sh/hello.txt https://transfer.sh/66nb8/hello.txt (Download the file) $ curl https://transfer.sh/66nb8/hello.txt -o hello.txt After the upload, the curl command returns a URL with a random token ("66nb8" in the above example). The problem is the other PC doesn't know the random token, and also I want to put the download command in cron. Is it possible for us to specify our own random token that we could use over and over? The file is encrypted so security concern with plaintext URL is not a problem. curl --upload-file ./hello.txt https://transfer.sh/3b2rd9n3kbew8jhs/hello.txt ...where 3b2rd9n3kbew8jhs is the random token chosen by the user. Thank you.

michael closed this issue

2026-01-19 18:30:03 +00:00

michael commented

2026-01-19 18:30:03 +00:00

@sheerun commented on GitHub:

I see it's currently hardcored to random: https://github.com/dutchcoders/transfer.sh/blob/master/transfersh-server/handlers.go#L350

@sheerun commented on GitHub: I see it's currently hardcored to random: https://github.com/dutchcoders/transfer.sh/blob/master/transfersh-server/handlers.go#L350

michael commented

2026-01-19 18:30:03 +00:00

@nl5887 commented on GitHub:

Because we're using random tokens, we can keep everything simple without using authentication. If we'll allow custom tokens, we need to add authentication, authorisation and all such. And we built this just for simple sharing.

@nl5887 commented on GitHub: Because we're using random tokens, we can keep everything simple without using authentication. If we'll allow custom tokens, we need to add authentication, authorisation and all such. And we built this just for simple sharing.

michael commented

2026-01-19 18:30:03 +00:00

@Jellby commented on GitHub:

I would like some kind of predictable URL too, though I'd prefer a full path with at least a couple of directory levels. Security and privacy are not primary concerns in this case: I don't mind if others can read the file and, if I choose a nontrivial name, I can be reasonably sure the file will not be overwritten (and it's not a big deal if it is). It could be something like mailinator.

@Jellby commented on GitHub: I would like some kind of predictable URL too, though I'd prefer a full path with at least a couple of directory levels. Security and privacy are not primary concerns in this case: I don't mind if others can read the file and, if I choose a nontrivial name, I can be reasonably sure the file will not be overwritten (and it's not a big deal if it is). It could be something like mailinator.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#368