int main(void){ printf("1 && 2 = %d\n", 1 && 2); printf("1 || 2 = %d\n", 1 || 2); }
What were you doing?
414 karma · joined January 9, 2013
int main(void){ printf("1 && 2 = %d\n", 1 && 2); printf("1 || 2 = %d\n", 1 || 2); }
What were you doing?
an important lesson, learn it fast.
I too am really amazed this isn't more prevalent as it is so easy to do, after discovering the vim ctrl-p [1] plugin I rarely go a day without using it.
> Best chance for a conviction is to pretend the wiretaps never happened.
And this is why PRISM coming to light is a good thing as it gives the defense another reason to question intent, in the scenario above it would be Bob and Alice asking why Dan was staking out their house and searching their cars.
I may be misinterpreting you, but I don't believe this is true. It only works if you find out other's have a similar or compatible secret.
If everyone found out you pick your nose and eat it, but no one else does it, how does that benefit the nose picker?
If bob finds out his boss hates him, and his boss finds out that he has racist tendencies, how does that benefit bob?
That said, I am not spending a cent until you ship and get a lot of positive reviews.
This is still better than password reuse as the plaintext doesn't disclose your other identified without further effort, however the users should be under no illusion of bullet-proof security.
For a given length it is possible to find all the inputs that could generate a possible hash relatively easy (cheap compared to other one-way-hashes).
> I do something similar via a shell
> echo "masterpassword gmail" | md5
Please do not do this, md5 is not a cryptographic hash and is relatively trivial to reverse. Ie; is possible for someone to discover your 'masterpassword' given any one of your passwords generated via this method.
If one of your passwords is leaked then it is possible for an attacker to brute-force this to find out a list of possible 'masterpassword foo' combinations (although not knowing the length increases the search space).
If one of those foos is 'gmail' for your gmail password then it is game over.
Even if your foo is not similar to the service, if the attacker is able to get 2 of your passwords then the search-space is much smaller (looking only at the overlap of the reverse of both md5 functions).
This may not be relevant if you only take a 'random' sub-sequence from the generated md5, thus only disclosing part of the hash to the attacker.
But at this point this is all pure speculation.
This way IP is kept relatively confidential, unless the viewer can remember every single detail and I doubt this unless they are very skilled with building electrical components. You could also get them to sign a non-disclosure agreement if you are concerned.
I also agree this seems unfair, many of the products on etsy don't seem to pass this same test.
However I am not so sure about a kickstarter imposed maximum, as certain projects (say non physical goods) can grow indefinitely (in terms of the quantity of the product given out) but have a minimum amount before they are able to bring the product to market.
I think it is more useful for the creator of the kickstarter to set a minimum and optional maximum.
I also quite like the idea of holding some amount in escrow until progress has been made (maybe anything over twice the minimum or similar).
In vim I get around this by habit, I stay in command mode and only enter insert mode for text entry, and then at the end of a 'unit' of text entry I return to command mode.
Thus I always know when I am in insert or command mode by asking 'am I currently entering text', for me hitting ctrl-c after finishing a sentence is part of the act of writing the sentence.
>"An human-machine interface is modal with respect to a given gesture when (1) the current state of the interface is not the user's locus of attention and (2) the interface will execute one among several different responses to the gesture, depending on the system's current state."
According to this definition an interface is not modal if the user is aware of the current mode at all times.
I am a vim user and have developed a habit of only ever being in insert mode when I am typing, after each unit of input I return to command mode. Using this approach modal error is very minimal.
I then remap away all the modes that cause me issues (record mode is a common cause of modal-error for me).
I commonly use 3 machines where I want sound (work,home,laptop) running a variety of different distros (arch,debian,ubuntu) and sounds works for me in all of them, mostly alsa although ubuntu is pulseaudio.
In the 99% case it just works, the only config I have to do is for my external DAC and that requires a few line config file (telling alsa to default to using my DAC rather than the first card it finds)