Tiny Core Extensions > TCE Talk

gmail failure

<< < (3/3)

Jason W:
softwaregurl-
Could you please send the original extension in tar.bz2 format to see if that would let it through.  There are going to be a lot of extensions with .sh script files in them and it would be good to find an archive format that will fly under the radar.

JW

Jason W:
Gmail doesn't allow .exe files to be sent, as well as others.  So I tried the bcrypt approach on putty.exe, which produced the file putty.exe.bfe.  I was able to upload it to gmail and download it with no problems.  So how about tarring up the files into a .tar.gz and then using bcrypt on it:

bcrypt extension.tar.gz

and send the password along with the email.  This should work as a hassle free means of uploading extensions.

tobiaus:
or you could just use "tinycore" as a password every time, that way it could be automated, and it's about as secure as sending it with the password right next to it.

i figured rot128 would be enough to get it past gmail, but there's no need to create a rot128 tool when bcrypt is readily available.

Jason W:
Bcrypt solved the problem with the extension in question.  From now on, bcrypt can be used on all submissions with the password tinycore as security is not the issue.

mikshaw:
So if it's decided that bcrypt is a workable permanent solution, I suppose that step should be added to
http://www.tinycorelinux.com/wiki/tiki-view_faq.php?faqId=3#q5


I like tobiaus's idea about a generic password.  Considering this is about getting past a faulty virus scan and not about security, a known password shouldn't be a problem.  I suppose it doesn't matter either way, though, since the password will only be used once by the email recipient.

Navigation

[0] Message Index

[*] Previous page