Commie 64s, Amigas, and... a website? Why isn't this a gopher site?
Re:Titanium is also very flexible.
on
The Sexiest Metal
·
· Score: 1
> This is why you won't see titanium in kitchen sinks, silverware or anywhere else where the metal needs to be thin, strong, and unflexible.
Hey, titanium silverware exists. I have a "snow peak" titanium spork. The handle's about.06" thick and definitely sturdy enough. The spoon portion by its shape is extremely sturdy.
Yes, sporks are the worst of both worlds, but at least this one's titanium.
No, crypt(1) is different from crypt(3). It was, what, a one-rotor Enigma machine or some such. Do a google search on 'crypt(1)'.
I'd call this not prior art since it wasn't really "application-independent", even if vi did have that -x option. Perhaps any of the encrypted file systems such as CFS would qualify.
All open source software used in critical applications is to become closed source immediately. Apparently hackers and terrorists can read through the source, if it's made available and may discover bugs, which can be exploited to harm the American way of life.
Removing access to the source code, and making reverse engineering illegal, is clearly preferable and safer.
Also interesting is the bit about not being allowed to hyphenate/pluralize any of the trademarks (e.g. "Com- mander Keen"). Guess they plan on using lousy search engines. You are also not allowed to misspell their trademarks. That's got to be a tough one to enforce. "You misspelled our trademark, Commander Keen(r)!" "How?!?" "--'Quake'!"
Raging.com most certainly _does_ support text browsers. It filters lynx out deliberately; if you lie about your browser type it'll let lynx in fine. Interestingly, w3m gets in without problems, although the first message you see is "This cookie was rejected to prevent security violation." For this lynx behaviour, and for the sad lousiness of its actual search results, I've been staying away from raging.com despite AltaVista's efforts to generate positive buzz.
Not exactly a back door, but rzsz from omen.com, which has a "complimentary" source version, had the following code inserted some time ago:
#ifndef REGISTERED /* Removing or disabling this code without registering is theft */ if ((Totfiles > 0) && (!Usevhdrs)) { sprintf(endmsg, "echo Unreg %s %s %ld %ld | mail rzsz@omen.com", Progname, VERSION, Totfiles, Totbytes ); system(endmsg);
In other words, it mails out what you're transferring and how big it is to Omen.
As I recall, it took the *BSDs some time to notice and yank rzsz from the ports tree. I wonder if this version is still supplied as a "package" for any of the Linuces?
> Well, I think the only "reasonable" (ehrm) incentive to "fake" results > is having a large keys/sec value, and if you have multiple id's, you > won't have that:) You guys are lacking imagination. If I were to hack the d.net client, I'd keep the key rate the same. I'd just make sure that if I found The Key, it'd tell me first, not distributed. Then I get all the prize money and I can donate money to charities that I think do more good than, say, ones de facto dedicated to ensuring rich people don't have to pay for their software.
Remember that strncpy() does NOT guarantee a null-terminated string. It adds the final '\0' only if the source string is shorter than the length parameter. strncpy(buf, input, sizeof(buf)); should always be followed by buf[sizeof(buf)-1] = '\0';
Or use strlcpy() if your OS has it (OpenBSD) and you don't need ANSI conformance.
> Hell, even GNU disses manpages in favor of "info"! ...which is high on the list of irritating GNU mistakes. Does anyone actually like all those "Warning: This man page is updated only occasionally" man pages GNU supplies? Beyond that, does anyone actually prefer using 'info' to man?
Slashdot Mirror
Commie 64s, Amigas, and ... a website? Why isn't this a gopher site?
Hey, titanium silverware exists. I have a "snow peak" titanium spork. The handle's about .06" thick and definitely sturdy enough. The spoon portion by its shape is extremely sturdy.
Yes, sporks are the worst of both worlds, but at least this one's titanium.
No, crypt(1) is different from crypt(3). It was,
what, a one-rotor Enigma machine or some such. Do
a google search on 'crypt(1)'.
I'd call this not prior art since it wasn't really
"application-independent", even if vi did have that
-x option. Perhaps any of the encrypted file systems
such as CFS would qualify.
All open source software used in critical applications
is to become closed source immediately. Apparently
hackers and terrorists can read through the source, if it's made available and may
discover bugs, which can be exploited to harm the American way of life.
Removing access to the source code, and making reverse engineering illegal,
is clearly preferable and safer.
Also interesting is the bit about not being allowed to
hyphenate/pluralize any of the trademarks (e.g. "Com-
mander Keen"). Guess they plan on using lousy search
engines. You are also not allowed to misspell their
trademarks. That's got to be a tough one to enforce.
"You misspelled our trademark, Commander Keen(r)!"
"How?!?" "--'Quake'!"
Raging.com most certainly _does_ support text
browsers. It filters lynx out deliberately; if
you lie about your browser type it'll let lynx
in fine. Interestingly, w3m gets in without problems,
although the first message you see is
"This cookie was rejected to prevent security violation."
For this lynx behaviour, and for the sad lousiness
of its actual search results, I've been staying
away from raging.com despite AltaVista's efforts
to generate positive buzz.
#ifndef REGISTERED
/* Removing or disabling this code without registering is theft */
if ((Totfiles > 0) && (!Usevhdrs)) {
sprintf(endmsg, "echo Unreg %s %s %ld %ld | mail rzsz@omen.com",
Progname, VERSION, Totfiles, Totbytes );
system(endmsg);
In other words, it mails out what you're transferring and how big it is to Omen.
As I recall, it took the *BSDs some time to notice and yank rzsz from the ports tree. I wonder if this version is still supplied as a "package" for any of the Linuces?
> Well, I think the only "reasonable" (ehrm) incentive to "fake" results :)
> is having a large keys/sec value, and if you have multiple id's, you
> won't have that
You guys are lacking imagination. If I were to hack the d.net
client, I'd keep the key rate the same. I'd just make sure that if
I found The Key, it'd tell me first, not distributed. Then I get
all the prize money and I can donate money to charities
that I think do more good than, say, ones de facto dedicated to
ensuring rich people don't have to pay for their software.
Remember that strncpy() does NOT guarantee a null-terminated string.
It adds the final '\0' only if the source string is shorter than the length parameter.
strncpy(buf, input, sizeof(buf)); should always be followed by
buf[sizeof(buf)-1] = '\0';
Or use strlcpy() if your OS has it (OpenBSD) and you don't need ANSI conformance.
> Hell, even GNU disses manpages in favor of "info"!
...which is high on the list of irritating GNU mistakes.
Does anyone actually like all those "Warning: This man page
is updated only occasionally" man pages GNU supplies?
Beyond that, does anyone actually prefer using 'info'
to man?
> Do you need to run it with a parameter or something?
No, you just need to replace the line that reads
if (delaytime = 0)
with
if (delaytime == 0)