It was the happy side effect from addressing another problem. The other problem being operating systems with shitty TCP stack implementations (*cough* Windows) that choose initial sequence numbers that weren't exactly random.
What happens when you pick a easily guessed sequence number? Somebody comes along and hijack's your connection.
The iPod is smaller... No, the Archos doesn't discretely in your pants pocket; well perhaps it discretely fits in the pocket of pants that have a waist of 45+ (US).
hehe, you can assign negative values to people using the karma bonus. That's pretty nice, you can now mod down the big-swinging-cock-because-i've-got-karma people.:-) yaaa
Those aren't Aqua widgets you're looking at in Chimera. Those are Mozilla's own widgets merely themed to look like Aqua. Chimera may be faster than IE, but the widget's it uses are still slower than native Aqua widgets (and they don't support all the cool things that good Cocoa widgets support, like spell checking).
Use brainpower, if you have a screen in front of you, it should shed enough light by itself onto the keyboard...
Actually, no. Your eyes dialate from looking at such a bright screen (even with the new autodimming of the new Powerbook it's still bright) so unless you have your the angle of your screen at an acute angle (to light the keys directly), it's much easier to see the keys if they're lighted.
*waits for the automatic down-modding due to negative Apple comments*
No, you're just not used a laptop or haven't thought through why they did this.
On the PowerBook section of the Apple site, it says that their 17" LCD has the same viewing area as a 19" CRT. Umm, that LCD has a max resolution of 1440x900 (with a bizarre aspect ratio of 16x10- why didn't they try to conform to HDTV with 16x9?), which is about HALF the area of the max resolution of a decent 19" monitor (say, a Viewsonic P95 w/ 1920x1440).
Umm, okay, their website said viewing area not max resolution so why don't you tone it back a little? Also, the reason they chose the 16x10 is because the resolution is 1440x900. 1440 / 16 = 90 and 900 / 10 = 90. The reason for the extra height is so you can have 16x9 material on the screen and still have room for a menubar and windowframe.
And the lighted keyboard- I think most people will recognize this as a gimmick at best. Who needs to see the keyboard to type?
No, it's quite useful. It's why those USB gooseneck lights can't stay on the shelves. First, not everyone types as well as you do, secondly, when it's dark, you can't see the keyboard to place your hands (and it's easier to glance down rather than try to feel for the dimples on the f and j keys).
I ran across this gem awhile ago, been saving it as a text clipping on my desktop for years now waiting for the perfect moment to post:
Halfway down the code there is a comment that looks something like this:
**SFS 07/05/96** Third day. Still no sign of an indented IF. Food and water is running out and the bearers are getting restless. I think Carruthers is going mad...
- Shane Smith <Shane.F.Smith@Healthnet.com> on proper code indentation, in comp.os.vms
I work for a small company too. Probably around 50 employees. Everyone gets a very sizable christmas bonus (even if they're new employees). The christmas party was great. Fully stocked open bar and very nice door prizes (one of them was five hundred dollars, cash). It's nice to work for a small company (we're in the defense industry so we have the added benefit of being stable too), everyone knows each other and everyone is friendly.
Either take the security argument to its true limits, or realize that practical choices need to be made and be quiet.
Keeping your kernel on r/o medium, turning off loadable kernel modules, and keeping your important binaries on r/o medium is a very practical choice and addresses the points that I brought up.
Presto! Completely secure binaries. No trojans. No false sense of security.
Yes yes, there is a point where the paranoia no longer pays off.:-)
I don't think my point is outrageous because with a list of known good checksums for lots of binaries available, it makes it very easy for those of ill-will to backdoor checksum utilities.
I think most people will agree that solutions posted in reply to my post such as booting a kernel from a r/o medium, turning off loadable kernel modules, and having important binaries (/bin/) on r/o mediums is not too paranoid (ie: hermit solution) but is very good security.
You don't understand that while perfection may not be possible, there is nothing wrong to point out the imperfections.
Fucking pompous amateurs.
That's a pretty large ego you've got there for a guy who is willing to settle for less. You don't even seem to want to work for a better solution.
You speak with such superiority when you fail to even point out good solutions like booting from known good read only mediums. Heck, even the anonymous cowards had something better to say.
What they don't say and what a lot of security folks forget to do is that they can't check your checksums of binaries on the same box. You need to copy the files to another box and check the checksums there with a known good version of your checksumming binary. The local version of your checksumming binary could have been compromised.
Heck, the utilities you used to pull the binary off the machine in question could have been compromised and may not be actually copying the binary in question, but a good version of the binary. The only way to check this would be to mount the drive on another machine and check it there... And if people aren't doing that (which it's a pain in the ass) all this website is going to do is give people a false sense of security.
So if you want to access PINE remotely, you must telnet in, and I don't need to explain why that's bad.
S/Key support is in most modern Unixes. S/Key + Telnet is very safe. And unless you use PGP (which I'm going to make a wild guess that you probably don't) you can't complain that people can read your unencrypted session and see your email.
Also, Java SSH clients that work in web browsers are a dime a dozen. Just check Freshmeat.
One last thing S/Key + Telnet is far less risky than https at a public terminal to the point that it's very acceptable and quite convenient.
There is a very good reason for not supporting sloppy focus in OS X. Think about it for a moment... How in the world would you get to the menu bar for an application without that app losing focus?
You'd do it the same way you'd access submenu's sloppily (try it, you don't need to go into a submenu exactly where it touches the real menu, you can slide it over the desktop). You track where the cursor is going. If it's heading torwards the menu bar at a fairly high rate of speed then don't switch focus.
It could be an option. The option to swap the left control and capslock keys on USB keyboards is supported and that particular option tends to annoy the hell out of everybody except for old school Unix folk and people who use emacs. They could simply make it an option like caps/control swap that nobody would ever run across unless they were specifically looking for it.
Unfortunately the sharks will just leave the lawyer alone. It's professional courtesy.
Re:All are missing the one thing I need (Mac OS X)
on
Thursday Release Party
·
· Score: 1, Redundant
I know you don't want to use third party tools, but for ssh is already installed and it's very easy to setup port forwarding. Heck, it's two lines of code in your ~/.ssh/config file (per host) and then tell Dreamweaver and GoLive to connect to localhost on whatever port ssh is listening. I'd say twenty seconds max to set it up. This is a very integrated solution that many people use for many things, it's not hacky at all.
Slashdot Mirror
It was the happy side effect from addressing another problem. The other problem being operating systems with shitty TCP stack implementations (*cough* Windows) that choose initial sequence numbers that weren't exactly random.
What happens when you pick a easily guessed sequence number? Somebody comes along and hijack's your connection.
The iPod is smaller... No, the Archos doesn't discretely in your pants pocket; well perhaps it discretely fits in the pocket of pants that have a waist of 45+ (US).
hehe, you can assign negative values to people using the karma bonus. That's pretty nice, you can now mod down the big-swinging-cock-because-i've-got-karma people. :-) yaaa
Those aren't Aqua widgets you're looking at in Chimera. Those are Mozilla's own widgets merely themed to look like Aqua. Chimera may be faster than IE, but the widget's it uses are still slower than native Aqua widgets (and they don't support all the cool things that good Cocoa widgets support, like spell checking).
Actually, no. Your eyes dialate from looking at such a bright screen (even with the new autodimming of the new Powerbook it's still bright) so unless you have your the angle of your screen at an acute angle (to light the keys directly), it's much easier to see the keys if they're lighted.
No, you're just not used a laptop or haven't thought through why they did this.
Umm, okay, their website said viewing area not max resolution so why don't you tone it back a little? Also, the reason they chose the 16x10 is because the resolution is 1440x900. 1440 / 16 = 90 and 900 / 10 = 90. The reason for the extra height is so you can have 16x9 material on the screen and still have room for a menubar and windowframe.
No, it's quite useful. It's why those USB gooseneck lights can't stay on the shelves. First, not everyone types as well as you do, secondly, when it's dark, you can't see the keyboard to place your hands (and it's easier to glance down rather than try to feel for the dimples on the f and j keys).
Original Usenet post by Shane for those interested.
I ran across this gem awhile ago, been saving it as a text clipping on my desktop for years now waiting for the perfect moment to post:
- Shane Smith <Shane.F.Smith@Healthnet.com> on proper code indentation, in comp.os.vms
Yeah! Apple used the trivial patch I made for the kernel and even plugged me in the announcement! :-D
Speaking about bots from this movie. The conceptual art of one of the robots looks remarkedly similar to a character from an older movie...
Amen.
I bet she likes it rough... :-)
I work for a small company too. Probably around 50 employees. Everyone gets a very sizable christmas bonus (even if they're new employees). The christmas party was great. Fully stocked open bar and very nice door prizes (one of them was five hundred dollars, cash). It's nice to work for a small company (we're in the defense industry so we have the added benefit of being stable too), everyone knows each other and everyone is friendly.
Keeping your kernel on r/o medium, turning off loadable kernel modules, and keeping your important binaries on r/o medium is a very practical choice and addresses the points that I brought up.
Yes yes, there is a point where the paranoia no longer pays off. :-)
I don't think my point is outrageous because with a list of known good checksums for lots of binaries available, it makes it very easy for those of ill-will to backdoor checksum utilities.
I think most people will agree that solutions posted in reply to my post such as booting a kernel from a r/o medium, turning off loadable kernel modules, and having important binaries (/bin/) on r/o mediums is not too paranoid (ie: hermit solution) but is very good security.
You don't understand that while perfection may not be possible, there is nothing wrong to point out the imperfections.
That's a pretty large ego you've got there for a guy who is willing to settle for less. You don't even seem to want to work for a better solution.
You speak with such superiority when you fail to even point out good solutions like booting from known good read only mediums. Heck, even the anonymous cowards had something better to say.
You've added nothing.
What they don't say and what a lot of security folks forget to do is that they can't check your checksums of binaries on the same box. You need to copy the files to another box and check the checksums there with a known good version of your checksumming binary. The local version of your checksumming binary could have been compromised.
Heck, the utilities you used to pull the binary off the machine in question could have been compromised and may not be actually copying the binary in question, but a good version of the binary. The only way to check this would be to mount the drive on another machine and check it there... And if people aren't doing that (which it's a pain in the ass) all this website is going to do is give people a false sense of security.
It was assumed in my post that people knew the correct definition of murder and/or had a dictionary close by...
Umm, did you even read my post? It's quite apparent that I know the differences between murder and killing.
It's not circular. While murder means killing, killing doesn't necessary mean murder. If you kill someone in an act of self defense, it is not murder.
Actually a correct translation from Hebrew shows that the commandment (Exodus 20:13) is really "Thou shalt not murder".
Varies between states. Age of consent for around the world.
S/Key support is in most modern Unixes. S/Key + Telnet is very safe. And unless you use PGP (which I'm going to make a wild guess that you probably don't) you can't complain that people can read your unencrypted session and see your email.
Also, Java SSH clients that work in web browsers are a dime a dozen. Just check Freshmeat.
One last thing S/Key + Telnet is far less risky than https at a public terminal to the point that it's very acceptable and quite convenient.
You'd do it the same way you'd access submenu's sloppily (try it, you don't need to go into a submenu exactly where it touches the real menu, you can slide it over the desktop). You track where the cursor is going. If it's heading torwards the menu bar at a fairly high rate of speed then don't switch focus.
It could be an option. The option to swap the left control and capslock keys on USB keyboards is supported and that particular option tends to annoy the hell out of everybody except for old school Unix folk and people who use emacs. They could simply make it an option like caps/control swap that nobody would ever run across unless they were specifically looking for it.
Unfortunately the sharks will just leave the lawyer alone. It's professional courtesy.
I know you don't want to use third party tools, but for ssh is already installed and it's very easy to setup port forwarding. Heck, it's two lines of code in your ~/.ssh/config file (per host) and then tell Dreamweaver and GoLive to connect to localhost on whatever port ssh is listening. I'd say twenty seconds max to set it up. This is a very integrated solution that many people use for many things, it's not hacky at all.