Hey, this is slashdot, where submitter don't read the original article, editors don't read the submission and posters... well, they just post and don't read anything at all. Might as well skip linking to any article at all.
Turbo C? Wordstar key bindings? You must be kidding. This veteran learned editing over a modem line using ex(1) or vi(1). Most of the time, I used ex(1) because the load on the VAX made vi(1) too slow.
The advogato [post is outdated. Since them quite a few things changed. Look at the code and the manual page:
ntpd uses the adjtime(2) system call to correct the local system time
without causing time jumps. Adjustments of 32ms and greater are logged
using syslog(3). The threshold value is chosen to avoid having local
clock drift thrash the log files. Should ntpd be started with the -d or
-v option, all calls to adjtime(2) will be logged.
After the local clock is synchronized, ntpd adjusts the clock frequency
using the adjfreq(2) system call to compensate for systematic drift.
Again, for the majority of use cases, OpenNTPD does achieve an accuracy that's good enough and even better than that.
Wrong again. It does do clock slowing or speeding up. Both to get the clock right and to compute a persistent clock frequency adjustment.
It does NOT just set the clock.
I don't know which version on what platform you were testing. Maybe your port was terribly done. But on OpenBSD it works like a charm for almost any purpose.
We're talking about the base openssh code here, not what some distro added to it.
Re:New, Problematic Protocol Introduced
on
OpenSSH 5.4 Released
·
· Score: 2, Interesting
The OpenSSH developers do not trust any X.509 code. The actual X.509 validation and trust decision mechanisms are pretty horiffic, and I'm glad they stayed away from that.
You don't have to throw away your X.509 certs, you can keep using them for other purposes.
Tab completion only applies to interactive sftp session, of course.
Re:New, Problematic Protocol Introduced
on
OpenSSH 5.4 Released
·
· Score: 3, Informative
No X.509 certificates are used. Please study the changes before you comment based on false assumptions.
Also, the agent protocol exists for quite a while now, it is not new.
Repeat after me: There is no such thing as a shortage in a free market.
Whenever you read a story about a shortage of something, 9 times out of 10 it's bull. Shortages only occur when artificial price controls are put on goods and services.
Reapeating something does not make it true.
But congrats. You have given us a source of infinite stupidity.
As if a datacenter like this would use a capped ADSL line...
You do not have to use the public internet. At some point, it becomes cheaper to use dedicated connections between your offices and datacenters.
You should de some background research on the history of C.
In the early 70's, a new language evolved from B. In these years, the new language was evolving quickly, but by 1973, it was mature enough to allow the Unix kernel to be rewritten in it. The makers called it C, from the same article:
By early 1973, the essentials of modern C were complete.
Who are you to say that it wasn't C?
And for certain, the yacc included in V6 was written in C, it generated C and it would soon be used to write C compilers.
The diff show only part of the files.
Jiri Slaby is not the sole copyrightjholder, so he cannot change the license without agreement of the other authors.
Slashdot Mirror
Yeah, I know, dutch double vowels are confusing...
Never knew they took safety with them.
Their inventory consists mostly of blackberries.
And PlayBooks!
Hey, this is slashdot, where submitter don't read the original article, editors don't read the submission and posters... well, they just post and don't read anything at all. Might as well skip linking to any article at all.
Dunno if I should laugh or cry
... and to promote that technology is cool, let's call in the help of the most uncool person in the world: QE II.
Turbo C? Wordstar key bindings? You must be kidding. This veteran learned editing over a modem line using ex(1) or vi(1). Most of the time, I used ex(1) because the load on the VAX made vi(1) too slow.
The advogato [post is outdated. Since them quite a few things changed. Look at the code and the manual page:
ntpd uses the adjtime(2) system call to correct the local system time without causing time jumps. Adjustments of 32ms and greater are logged using syslog(3). The threshold value is chosen to avoid having local clock drift thrash the log files. Should ntpd be started with the -d or -v option, all calls to adjtime(2) will be logged. After the local clock is synchronized, ntpd adjusts the clock frequency using the adjfreq(2) system call to compensate for systematic drift.
Again, for the majority of use cases, OpenNTPD does achieve an accuracy that's good enough and even better than that.
Wrong again. It does do clock slowing or speeding up. Both to get the clock right and to compute a persistent clock frequency adjustment. It does NOT just set the clock. I don't know which version on what platform you were testing. Maybe your port was terribly done. But on OpenBSD it works like a charm for almost any purpose.
Not true. It is simple, but it does slewing and rules out bad servers etc.
One typical use would be where you want people to use sftp, but do not want to give them shell access, any shell for that matter.
Oops. You're right. Still tab completion in te FA is about tab completion in interactive sftp sessions.
We're talking about the base openssh code here, not what some distro added to it.
The OpenSSH developers do not trust any X.509 code. The actual X.509 validation and trust decision mechanisms are pretty horiffic, and I'm glad they stayed away from that. You don't have to throw away your X.509 certs, you can keep using them for other purposes.
Tab completion only applies to interactive sftp session, of course.
No X.509 certificates are used. Please study the changes before you comment based on false assumptions. Also, the agent protocol exists for quite a while now, it is not new.
You have to look at it from his perspective.
Basically his perspective is "Someone else has money. I want it." ...
Not the best perspective by my standards, but he has many times more money than I do, so who am I to say he's a F*#@#ing idiot.
Phrased differently: "there's a lot of money in the world that's not in my pocket. The injustice!"
Repeat after me: There is no such thing as a shortage in a free market. Whenever you read a story about a shortage of something, 9 times out of 10 it's bull. Shortages only occur when artificial price controls are put on goods and services.
Reapeating something does not make it true. But congrats. You have given us a source of infinite stupidity.
You mean a "plurality of exclamation marks"
You now will be escorted off-site.
As if a datacenter like this would use a capped ADSL line... You do not have to use the public internet. At some point, it becomes cheaper to use dedicated connections between your offices and datacenters.
I think you missed the point. The bug is in the code generated by yacc, which can end up anywhere.
In the early 70's, a new language evolved from B. In these years, the new language was evolving quickly, but by 1973, it was mature enough to allow the Unix kernel to be rewritten in it. The makers called it C, from the same article:
Who are you to say that it wasn't C?
And for certain, the yacc included in V6 was written in C, it generated C and it would soon be used to write C compilers.
This is NOT true. All key material generated with the patch is potentailly predicatble. This includes client SSL certs and personal ssh keys.
The diff show only part of the files. Jiri Slaby is not the sole copyrightjholder, so he cannot change the license without agreement of the other authors.