You know other source control systems, and presumably git also, have an
excludes list which can contain wildcards. It comes prepopulated with eg
*.o - as you probably dont want to check them in.
I think you could classify this as a git bug (or more probably a mistake in
how github are
Hi Folks,
I am new to the list and have in interest in encryption, but not much
experiance in breaking/testing or a details understanding of modern methods.
I am interested in developing some technology to allow a user to
communicate as securly as possible between a termial on an unsecure
On 28 January 2013 13:37, Paul Christian pho...@gmail.com wrote:
Hi Folks,
I am new to the list and have in interest in encryption, but not much
experiance in breaking/testing or a details understanding of modern methods.
I am interested in developing some technology to allow a user to
On 28/01/13 16:37 PM, Paul Christian wrote:
Hi Folks,
I am new to the list and have in interest in encryption, but not much
experiance in breaking/testing or a details understanding of modern methods.
I am interested in developing some technology to allow a user to
communicate as securly as
AB == Adam Back a...@cypherspace.org writes:
AB You know other source control systems, and presumably git also, have
AB an excludes list which can contain wildcards. It comes prepopulated
AB with eg *.o - as you probably dont want to check them in.
For git, the file is called .gitignore. You
To rephrase, I don't understand why anyone would push their /home/user /
backup git repository to a public one on GitHub :)
On Mon, Jan 28, 2013 at 3:49 AM, ianG i...@iang.org wrote:
On 28/01/13 05:36 AM, Eitan Adler wrote:
On 27 January 2013 21:34, Patrick Mylund Nielsen
On Mon, Jan 28, 2013 at 8:37 AM, Paul Christian pho...@gmail.com wrote:
... not much experiance ... or a details understanding of modern methods.
I am interested in developing some technology ...
One summary of why that may be hard:
Peter Gutmann wrote:
the reason why Bleichenbacher attacked v1.5
rather than OAEP is because use of the latter is [...]
compared to v1.5, [...]
Please correct me if I'm wrong. My point is that the highly significant
academic contributions (among which I would put Bleichenbacher attack)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/2013 09:34 PM, Patrick Mylund Nielsen wrote:
I don't understand how you can accidentally check in ~/.ssh to
your repository, or at least not notice afterwards. Hopefully the
OpenSSL authors won't do that!
There are people who set up
On Sat, 26 Jan 2013, ianG wrote:
Apologies in advance ;) but a cryptography question:
I'm coding (or have coded) a digital signature class in RSA. In my research
on how to frame the input to the RSA private key operation, I was told words
to effect just use OAEP and you're done and dusted.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/2013 10:24 AM, Patrick Mylund Nielsen wrote:
To rephrase, I don't understand why anyone would push their
/home/user / backup git repository to a public one on GitHub :)
For the use case of personal config files, it makes setting up one's
Sorry for the top posting.
Are you sure that you want to do something in this field before
reading in depth anything ? Crypto is no more magic art. Anyway, it
always better to use something that most expert consider, or better,
have some proof that it is rock solid, in the modern crypto sense.
12 matches
Mail list logo
