10001110100110101
Hey, this ssh thing is great! I feel so safe and secure now..
Actually, weirDo came across a web based aplication called Arson which allows a user to log in and open a port in a system's firewall remotely. I've been looking for it, but I can't find it anywhere (of course, any searches for Arson result in a lot of mishits).
I'll have to look into that if I plan on accessing the server from many different remote locations..
I found this page while trying to figure out why I'm missing out on a few megs of RAM. Now I know that some of it's being used for other stuff, but I need to know what that "other stuff" is.. (Like reserved. Reserved for what?)
[0 Comments]
Hey hey! It was a lot easier than I thought it would be. Anyway, apparently weirDo wrote the script himself, which would explain why I couldn't find any references to it anywhere on the net. What it does is opens up specific ports on the server for anyone who has a password. I said "log in" but that's not true. They don't actually log into the system, they just trigger a script to open a port. Having the Arson access does not grant access to the server to the user, they still need a login and password on the server as well.
[0 Comments]
Hey,. weirDo sent me the arson script and.. my it's really short. I'm going to have to rewrite it to work for my site, but man, it's really short. *looks* Oh, that's why. It's using a module.
Anyway, PRQ was telling me why TARGETs are not used anymore, so I figure that I should actually start making everything standards compliant again. I remember doing this many many years ago and eventually gave up since the standards kept changing. That and the fact that IE was not standards compliant! *shakes fist*
[0 Comments]
Since I was thinking about security, I decided to do a bit of snooping around and came across this site. Hmm.. more ideas for web projects? *rubs hands*
I'll add it to the pile.
[0 Comments]
I was wondering why I'd have to change the TARGET attributes in my pages when I remembered that all of my pages that use the TARGET attribute actually require javascript to access those pages! Well sonofagun. Problem solved! This should make the changeover that much easier.. (Now I have to make sure that it works in the various flavors of javascript..)
[0 Comments]
Hmm, I think it should be working now. I'm not quite sure if it'll work with the older browsers. *shrugs* I don't have time to test it out right now unfortunately.
At least I got rid of all the TARGET attributes.
[0 Comments]
Ugh, with these changes I'm making, NS4 is working less and less with this site.
Actually, those who disable javascript will get a better (albeit non CSS) experience. I probably will throw in some checks to make sure none of the javascript runs with pre NS4/IE4 browsers. It's cleaner, and there's just way too many things to keep track of. Also, I think I might be able to make the page HTML 4.0 compliant again!
[0 Comments]
Tuesday, September 02, 2003 at 20:15:46 (UTC)
Seems like an ass-about way of approaching a problem. If you can already log in to make the firewall change, then surely you don't need to change the firewall, unless you're wanting to then expose ports that are not properly secured.
llamatronic
Tuesday, September 02, 2003 at 21:01:21 (UTC)
Actually, the problem is that the firewall clobbers any IP that it doesn't recognize, so if I'm at a client site or on vacation, I can't access the server unless I change the firewall, which requires access to the server.
Normally, I do this through an open third party server which I currently have access too, but when that account goes, I have no way of changing the firewall settings.
QYV
Friday, September 05, 2003 at 16:20:59 (UTC)
Indeed - my point was that if you have to be that careful with whatever ports you want to control, you're better off finding a more secure solution for those services than attempting to restrict access to them via a web-based solution. Particularly an externally-facing web solution.
(imo)
lloomatroon