11–20 of 32 posts
curl -s https://some.probably.malicio.us/site/ |sudo bash Yup, that is exactly what the world needs.
curl -s https://some.probably.malicio.us/site/ |sudo bash Yup, that is exactly what the world needs.
On the other hand, looking at the source (which hilariously checks and warns if curl doesn't exist) you could just download https://pagekite.net/pk/pagekite.py put it on your $PATH manually.
The thing that makes me feel odder is that pagekite.py is just a bunch of base64 compressed python scripts - if you are going to put your .py script on a user's machine, are there really that many savings in compressing all the python code?
Founder of PageKite here. I'm more than happy to answer any questions folks may have. :-)
Lack of coffee question for you. I've registered and am playing with this and I'm looking to tap into not only IIS but also node apps running on say, localhost:8999. Is that possible with this product or is it purely sitting on the IIS instance?
Earlier quoted context omitted.
Lack of coffee question for you. I've registered and am playing with this and I'm looking to tap into not only IIS but also node apps running on say, localhost:8999. Is that possible with this product or is it purely sitting on the IIS instance?
Should be no problem. You can point to any local port, and you can run multiple "kites" at the same time (assign public names to mupltiple ports at once). Just make sure your apps generate relative URLs and don't contain absolute IPs and ports and it should be smooth sailing.
curl -s https://some.probably.malicio.us/site/ |sudo bash Yup, that is exactly what the world needs.
Is this really less transparent than running a rpm or installer .app? On the other hand, looking at the source (which hilariously checks and warns if curl doesn't exist) you could just download https://pagekite.net/pk/pagekite.py put it on your $PATH manually. The thing that makes me feel odder is that pagekite.py is just a bunch of base64 compressed python scripts - if you are going to put your .py script on a user'…
Earlier quoted context omitted.
Yeah, that needs changing ASAP.
I get that alot. But this is actually easier to audit than install.exe or the shell scripts embedded in a .deb or .rpm (which, incidentally, also run as root). It looks scary, but it really isn't. Or rather, it's no scarier than most of the other ways to add software to the common desktop operating systems. Edit: and for those who care, there are .rpm and .deb packages available, or you can grab the source from githu…
It also concerns me that the author of security conscious software isn't concerned by this.
I'd sort of like to not have to use it - I'd prefer to just tunnel through my cable modem, but some lock down from Time Warner makes this much harder than it should be.
I'd used the localtunnel service from twilio earlier, and like that. But Pagekite is better in a few ways.
1. the naming - foo.pagekite.me far reduces any potential collision I'd get vs the localtunnel approach of xpkf82.localtunnel.com getting reused accidentally.
2. Pagekite can follow me - go to the local cowork space, run pagekite, and foo.pagekite.me now points to my new IP address at the cowork space.
3. SSL - I get https:// forwarding by default
I'm using this for some facebook work, and have my facebook app stuff pointing to foo.pagekite.me while I'm in dev, and it's working great.
I do find their control panel / acct mgt slightly confusing - what a 'kite' is wasn't really apparent to me at first, and 'remaining bandwidth' vs how much I've used wasn't something I could easily see (the numbers are at opposite ends of the screen in different font sizes). Some of this may be because I'm new to the service, but also because I just don't go there that much (little need).
Thanks pagekite!
Recently became a paying pagekite customer. Couple of thoughts here: I'd sort of like to not have to use it - I'd prefer to just tunnel through my cable modem, but some lock down from Time Warner makes this much harder than it should be. I'd used the localtunnel service from twilio earlier, and like that. But Pagekite is better in a few ways. 1. the naming - foo.pagekite.me far reduces any potential collision I'd get…
Earlier quoted context omitted.
I get that alot. But this is actually easier to audit than install.exe or the shell scripts embedded in a .deb or .rpm (which, incidentally, also run as root). It looks scary, but it really isn't. Or rather, it's no scarier than most of the other ways to add software to the common desktop operating systems. Edit: and for those who care, there are .rpm and .deb packages available, or you can grab the source from githu…
Further to bensummer's link, packages allow a package manager to manage the software. Update, delete etc is all taken care of. It also concerns me that the author of security conscious software isn't concerned by this.
That said, I do consider this to be a temporary measure while the software is maturing to the point that I can get it accepted into the mainstream distros and build proper win/mac packages. That would be better for everyone, both from a usability and security standpoint.
We are a very small team (usually just me) and these things take time.