I don't think it is possible using this exploit... This exploit requires at the very least the HFS+ metadata. Not so sure about the resource fork, but the others say that is where the other metadata (entry point (i.e. main) etc.) goes.
And yes, I have to agree that is a significant flaw. The law of least surprise is a law of usability, it states that consistency is intuitive... This behaviour is completely counterintuitive.
I wonder how it is being dealt with in Apple now...
Euclidean geometry can be modelled using complex numbers quite well.
There's also modular geometry, which has two complex axes -- four axes in total. (We have this geometry to thank for the solution of whether there are no solutions for a^n + b^n = c^n for positive integers a, b, c, n and n > 2)
In a world where everything is statically linked...
SUBJECT: ALERT! glibc buffer overflow vulnerability with privillege escalation....
SOLUTION: 1. Update to glibc 2.3.4. 2. Recompile everything.
That is not the only reason why we use dynamic linking. You also exaggerate the dependencies of apps... Binaries should be linked to minor-version-specific symlinks rather than to revision-exact. The Un*x/Linux method of dealing with dynamic libraries is actually quite good, as compared to versionless Win32 DLL hell. (Though I hear.NET brings versioned libraries)
In a surprise announcment, yesterday, Apple Computer said that it is finally doing away with the keyboard. Apple stated that the microcomputer user has suffered too long with this awkward and inefficient input device. According to an Apple spokesperson, the technology for replacing the keyboard with only a mouse is here and the computer user is ready for it. The spokesperson said that Apple has received a steady stream of complaints over the years about the need to constantly move the hands between the Mac keyboard and mouse. "The solution was obvious - do away with the keyboard completely."
Acknowledging that there are still a few Mac applications that depend on textual input in addition to graphical manipulation, Apple said the poor people stuck with such outdated technology have not been forgotten. They are introducing the Spinning Alphabet Wheel (SAW) to replace the keyboard. The SAW is a screen display object consisting of concentric circular strips showing all of the characters which normally appear on the keyboard. The wheel rotates continuously under character selector windows. The user selects a character by placing the mouse pointer in the appropriate window at the same time as the desired character is about the appear. "...and, ta-da, the selected character appears on the screen just as though it had been typed on an old fashioned keyboard."
"This is a marvelous new technology with plenty of room for growth." said the spokesperson. For example, the user can configure separate wheels for vowels vs. the consonants. Or, digits can be placed on their own special low speed wheel. "We have conceptualized the keyboard as a big, bulky menu selection device and replaced it with dynamic display menus instead. Apple will eventually replace all menus with their new Rotating Wheel Technology (RWT)."
When asked why the wheels have to rotate, the spokesperson said that Apple's engineers had considered using conventional "point-and- click" technology for the wheel. "However," the Apple spokesperson said, "we feel that this type of operation is too complicated for the typical Mac user. So, we have done away with the mouse button too. It is still hard for us to believe that the IBM world has stepped backwards in technology by providing two or more buttons to confuse the user. The IBM compatible sector, apparently, has not yet recognized that 95% of computer usage is devoted to experimenting with different fonts and character styles in documents"
Asked if this new technology would reduce the price of the typical Mac computer, the spokesperson countered that it would probably increase the price of the Mac. "After all, display space is already scarce on the current screen. We will now deliver Macs with two screens - one for the normal display and a larger one for the multitude of rotating wheels the user needs to access." Apple said that the user who is confused by complicated devices such as keyboards and mouse buttons will gladly pay a premium to avoid them. "In fact, the easily-confused user is our best customer" replied the spokesperson. "Not only are we doing away with the pesky keyboard, but we are also giving them something they have demanded for a long time - more screen space. This is definitely a win-win situation."
Beta testers of the new technology were impressed by its ease of use, but said there are still some minor problems to work out. For example, one tester left his machine unattended with the uppercase character wheel spinning at medium speed. While he was away somebody must have jarred his desk, moving the mouse pointer into the selector window. When he got back he found that his Word document now had one huge paragraph consisting of all of the characters of the uppercase alphabet repeated 2,539,987 times. "At first glance, this appeared to be a big problem. But, I formatted the new paragraph with 33 different fonts and 11 different type styles and it looked great. I hope that Apple fixes this problem before they release it, because these accidents can greatly increase the time spent formatting documents."
What if, unexpectedly, a car's engine stalls? If computers could brake immediately, there is still the issue of decelerating...
Centralised autodriving has other advantages as well... for instance, you could have more efficient route planning. Knowing how crowded other roads are is very useful. What is the point of travelling the shortest path if you have to travel at snail's pace?
Applications do not cache passwords. If you see the nice prompt asking you for an administrative password, it should be coming from the system. (There are ways of verifying this... Set your account to use the Blue colour scheme, set your (real) root account to use the Graphite colour scheme. Any dialogue boxes or windows with Graphite widgets are running as root)
As for asking for the original password, that is because of Keychain. That one is encrypted with your original password.
As for apple.com caching the password... Well, it is quite simple to prove/disprove that: put the OS X machine behind a firewall, and log any attempts to connect to a machine in apple.com network.
Go with the de facto standard where there is no de jure standard. Otherwise, go with the de jure standard.
In other words: There is no formal standard for C++ name mangling. So go with whatever's popular. There is a formal standard for (X)HTML and CSS though, so go for that.
Consider this: for geniuses by geniuses. Have you considered that the software might not be aimed at the average person?
But enough about that. Consider most things average users do. Or rather, the things they use. They are usually quite simple, doing one task well. But computers are designed to do many tasks. Software is designed to do many tasks. It is no wonder that user interfaces become complex...
Slashdot Mirror
SPARC is an open CPU, probably more so than x86 or PowerPC.
Look at the number implementations.
Innovative? I'd say no. (Except in terms of business.)
Resilient? Maybe. Then again, the world of PC practically revolves around Microsoft, so they don't really have much change to deal with.
More than that, it gives 2 years for GNOME/KDE/X11/GNU/Linux to actually innovate.
Pah. I saw the real code just a few minutes ago.
[ecode]
struct votetally
{
int democratCount:1;
unsigned long long int republicanCount;
};
[/ecode]
After testing it by setting all bits to 1, these were the results:
Votes:
Democrats: -1 votes, -5.421010862e-18%
Republicans: 184467440737095515, 100.00%
I don't think it is possible using this exploit... This exploit requires at the very least the HFS+ metadata. Not so sure about the resource fork, but the others say that is where the other metadata (entry point (i.e. main) etc.) goes.
.extension was inherited from NeXT.
And yes, I have to agree that is a significant flaw. The law of least surprise is a law of usability, it states that consistency is intuitive... This behaviour is completely counterintuitive.
I wonder how it is being dealt with in Apple now...
Haha, only serious...
Euclidean geometry can be modelled using complex numbers quite well.
There's also modular geometry, which has two complex axes -- four axes in total. (We have this geometry to thank for the solution of whether there are no solutions for a^n + b^n = c^n for positive integers a, b, c, n and n > 2)
In a world where everything is statically linked...
...
.NET brings versioned libraries)
SUBJECT: ALERT! glibc buffer overflow vulnerability with privillege escalation.
SOLUTION:
1. Update to glibc 2.3.4.
2. Recompile everything.
That is not the only reason why we use dynamic linking. You also exaggerate the dependencies of apps... Binaries should be linked to minor-version-specific symlinks rather than to revision-exact. The Un*x/Linux method of dealing with dynamic libraries is actually quite good, as compared to versionless Win32 DLL hell. (Though I hear
* Alarms sound in The Redmond Campus *
ANNOUNCER: Attention Employees! Nuclear Warhead approaching!
BILL GATES: Quickly, crash the navigation systems!
TECH #2398: I've tried all the standard tricks! I cannae crash!
TECH #2399: Probing... It runs... The M-OS sir.
BILL GATES: M-OS??
TECH #2398: You know, the Fruit?
BILL GATES: Which fruit??
TECH #2399: The red one the students give teachers?
BILL GATES: Damn you Mattintosh!
* The blast destroys the Microsoft Campus, taking MSN and Hotmail with it *
Agreed. Processors should be labelled in bogomips instead!
Apple's own documentation might be just as good:
Reference Library
Cocoa
Getting Started
Fundamentals
API reference
Must read:
The Objective-C language
Overview of a SimpleCocoaApp
Developing Cocoa Objective-C Applications: A Tutorial
The US Dollar has no backing. Its value is defined in terms of itself. Or so I'm told.
Hi. You must be new here!
I assume it is the language from the sig: "Ph-nglui mglw'nafh Gates R'chmd wgah'nagl fhtagn."
Perhaps it is 'vrgwr!wrkp*rwq' (! is a glottal stop, * is a click), which is normally translated as "Gorge my eyes out with a spoon"
What if, unexpectedly, a car's engine stalls? If computers could brake immediately, there is still the issue of decelerating...
Centralised autodriving has other advantages as well... for instance, you could have more efficient route planning. Knowing how crowded other roads are is very useful. What is the point of travelling the shortest path if you have to travel at snail's pace?
Applications do not cache passwords. If you see the nice prompt asking you for an administrative password, it should be coming from the system. (There are ways of verifying this... Set your account to use the Blue colour scheme, set your (real) root account to use the Graphite colour scheme. Any dialogue boxes or windows with Graphite widgets are running as root)
As for asking for the original password, that is because of Keychain. That one is encrypted with your original password.
As for apple.com caching the password... Well, it is quite simple to prove/disprove that: put the OS X machine behind a firewall, and log any attempts to connect to a machine in apple.com network.
Hmm, how did that get past the yelling filter... Hmm...
Go with the de facto standard where there is no de jure standard. Otherwise, go with the de jure standard.
In other words: There is no formal standard for C++ name mangling. So go with whatever's popular. There is a formal standard for (X)HTML and CSS though, so go for that.
Excerpted from ~/Library/Preferences/com.apple.itunes.eq.plist:
I see a huge chunk of Base64 encoded data. It is an XML file, 90% of which is Base64 data.
It is very, very easy to take a file and put a XML wrapper around it.
Let's just get this out of the way, some pro-capitalist is bound to say it:
Capitalism (or rather, corporatism) is, excluding religion, the single largest voluntarily cooperative effort in the history of mankind.
But I'm sure we can transcend groups vs. groups as well. We are One Species, We are One People; surely we can all cooperate. (Or learn to tolerate.)
Consider this: for geniuses by geniuses. Have you considered that the software might not be aimed at the average person?
But enough about that. Consider most things average users do. Or rather, the things they use. They are usually quite simple, doing one task well. But computers are designed to do many tasks. Software is designed to do many tasks. It is no wonder that user interfaces become complex...
Memory management in C: You do it. Mostly.
If you don't want to care about it, don't use C.
The people who hate the new finder are likely Classicists who want their Spatial Finder back.
/., when there was a GNOME 2.6 thread, there were many, many posts dissing the Spatial Nautilus.
And just recently on
So...? Different people have different tastes. Appealing to everyone is near impossible. Ask them politicians.
Pigeon is just the carrier. However, checksumming is simple enough to do.
1. Extract DNA.
2. Compare DNA.
3. Extract packet.
4. Checksum packet.
However, if you insist on using hashes...