[Sorry for the delay in responding. I'm in the middle of changing jobs
and moving across the continent, so my availability going to be somewhat
sporadic.]
I've just posted my reply here: https://bitbucket.org/kang/python-
keyring-lib/issue/64/new-cryptedfilekeyring-doesnt-
follow#comment-1588956
Launchpad mangled my example code. Here it is again:
>>> def enc(password):
... return AES.new("0123456789abcdef", AES.MODE_CFB, "\0"*16) \
... .encrypt(password).encode('hex')
...
>>> enc("a")
'6a'
>>> enc("ab")
'6af9'
>>> enc("abc")
'6af9bb'
>>> enc("abc0")
'6af9bb62'
>>> enc("
"I don't think [insert arbitrary misuse of crypto here] is horrifically
insecure here"
This is wrong-headed thinking. If I had a dollar for every time a
programmer said that and was wrong, I would be rich.
Strong crypto is only strong if you follow the instructions *exactly*.
Everything else is
Hmm. It looks like python-keyring's CryptedFileKeyring uses weak
cryptography, and your pull request effectively asks me to change
PyCrypto in order to hide that fact. Obviously, I'm not going to do
that, so I've rejected your patch.
This is a terrible way to initialize a cipher from a password:
I think this bug should be reopened. RFC 2812 ("Internet Relay Chat:
Client Protocol") states:
IRC messages are always lines of characters terminated with a CR-LF
(Carriage Return - Line Feed) pair, and these messages SHALL NOT
exceed 512 characters in length, counting all characters incl
On Thu, Nov 17, 2011 at 06:24:43PM -, Sebastien Bacher wrote:
>Nobody is denying that there are requests for those changes, but you can
>find lot of users requesting any change and often a non trivial number
>of users with a different or conflicting opinion ;-) Reality is that
>people are diffe
Allison: The problem expressed in this bug report is that every time a
user complains about having a bad experience with the UI, the response
has been, "WONTFIX". I don't see how your comment changes any of that.
The fact that you characterize this thread as "unhealthy" just
illustrates the prob
On Wed, Nov 09, 2011 at 07:41:38AM -, Mark Shuttleworth wrote:
>On 08/11/11 19:31, kfsone wrote:
>> However: The direction and changes of 11.x *suggest* to us that Ubuntu
>> is swapping from desktop to sub-desktop focus for it's primary
>> distribution.
>
>No. What's happening is that the new f
> As far as I can tell, this is all about one issue - moving the
launcher.
I think the launcher just illustrates a deeper problem with the *attitude*
that's been steering Unity development: making the experience better for 180
million hypothetical new users, while neglecting the experience of the
> As a point of reference, Windows 8's Metro user interface is going to
> provide a "Windows Classic" workspace for backwards compatibility. This is
> an area that Microsoft has consistently gotten right over the years...
Why do we always point to Microsoft and Apple as if they're somehow a
refere
> We have about 20 million users today. We want 200 million users by 2014.
> The extra 180 million users are not in the Ubuntu community today, so you
> can in a sense say that it's true - Unity was not developed for the Ubuntu
> community of today, it was developed with love for the Ubuntu communi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884897
Title:
Touch input generates RawMotion & history with incorrect valuators
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Public bug reported:
When using a touchscreen, xserver generates incorrect RawMotion events
when some of the axis values have not changed since the last event.
This is for evdev with absolute positioning.
The bug is *not* present in the Debian xserver-xorg-core (2:1.7.7-13)
package.
[I will edi
Works for me now (built from source on natty). Thanks, everyone!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194916
Title:
libmikmod mis-renders ImpulseTracker (.it) files on amd64
To manage not
This is against version 0.0.4-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799190
Title:
fails when device name contains whitespace
To manage notifications about this bug go to:
https://bugs.lau
I've attached a patch to fix this bug.
** Patch added: "fix-pct-scanner-script-quoting.patch"
https://bugs.launchpad.net/ubuntu/+source/pct-scanner-scripts/+bug/799190/+attachment/2174277/+files/fix-pct-scanner-script-quoting.patch
--
You received this bug notification because you are a memb
Public bug reported:
Binary package hint: pct-scanner-scripts
pct-scanner-script doesn't work at all when the scanner device name
contains a space.
Output of "scanimage -L":
device `fujitsu:ScanSnap S1500:24768' is a FUJITSU ScanSnap S1500 scanner
device `hpaio:/usb/hp_LaserJet_3015?serial=
And the butchered version...
** Attachment added: "Rendered using libmikmod2 3.1.11-a-6.3 on Ubuntu/amd64"
https://bugs.launchpad.net/ubuntu/+source/libmikmod/+bug/194916/+attachment/2006384/+files/amd64.ogg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
There's a good sample here: (fallacius_gear.it):
http://modarchive.org/module.php?41179
The melody plays fine on i686, but gets completely butchered on amd64.
Deleting debian/patches/CVE-2007-6720.patch and rebuilding libmikmod2
makes the problem go away, but obviously that's not what we want.
*
** Summary changed:
- background music doesn't play correctly
+ libmikmod mis-renders ImpulseTracker (.it) files on amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194916
Title:
libmikmod mis-r
*** This bug is a duplicate of bug 595886 ***
https://bugs.launchpad.net/bugs/595886
** This bug has been marked a duplicate of bug 595886
/etc/init.d/resolvconf start clobbers resolv.conf information
* You can subscribe to bug 595886 by following this link:
https://bugs.launchpad.net/ubu
One workaround is to open up gconf-editor, go to
/system/networking/connections/#/vpn and add keys for the options you
want.
--
network-manager-openvpn does not support all options supported by openvpn
https://bugs.launchpad.net/bugs/364101
You received this bug notification because you are a mem
** Changed in: pycrypto
Milestone: None => 2.1.0
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: pycrypto
Milestone: None => 2.1.0
--
generating a 160-bit DSS key leads to eternal loop
https://bugs.launchpad.net/bugs/247846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Changed in: pycrypto
Milestone: None => 2.1.0
--
pycrypto-2.0.1 uses md5 & sha1 modules which will be deprecated in 2.6/3.0
https://bugs.launchpad.net/bugs/269429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
We believe this bug has been fixed in PyCrypto v2.1.0, which can be
obtained from http://www.pycrypto.org/
** Changed in: pycrypto
Status: Fix Committed => Fix Released
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You rece
We believe this bug has been fixed in PyCrypto v2.1.0, which can be
obtained from http://www.pycrypto.org/
** Changed in: pycrypto
Status: Fix Committed => Fix Released
--
generating a 160-bit DSS key leads to eternal loop
https://bugs.launchpad.net/bugs/247846
You received this bug notif
We believe this bug has been fixed in PyCrypto v2.1.0, which can be
obtained from http://www.pycrypto.org/
** Changed in: pycrypto
Status: Fix Committed => Fix Released
--
pycrypto-2.0.1 uses md5 & sha1 modules which will be deprecated in 2.6/3.0
https://bugs.launchpad.net/bugs/269429
You
** Changed in: pycrypto
Status: Incomplete => Invalid
--
SHA256-HMAC debian version is not compatible with upstream package
https://bugs.launchpad.net/bugs/246889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Generating 160-bit DSA keys is now disallowed; DSA.generate now accepts
only multiples of 64 between 512 and 1024, inclusive. Feel free to re-
open this bug if you need something more than that.
http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=commitdiff;h=ec73777d49de6a53d0302d23c522070a0
FWIW, from my reading of the DSA spec, you should never be generating
160-bit DSA keys; The first parameter to DSA.generate should be
multiples of 64 between 512 and 1024.
I'm still looking into this.
--
generating a 160-bit DSS key leads to eternal loop
https://bugs.launchpad.net/bugs/247846
Yo
"Standard pycrypto-2.0.1" exhibits the incorrect behaviour described in
Bug #191683, and this is probably just an unfortunate consequence of
that. The self-tests (using the test vectors from RFC 4231) don't
detect any problem with the latest SHA256 code in the git repository.
I'm closing this bug
This fix was committed a while ago (before I started maintaining
PyCrypto), but here's the change in the git repository:
http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.0.x.git;a=commitdiff;h=b41b1e021bd53772f712335de5c6eb8488fd08c5
** Changed in: pycrypto
Assignee: (unassigned) =>
Oops, I meant bug #191683
--
SHA256-HMAC debian version is not compatible with upstream package
https://bugs.launchpad.net/bugs/246889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Is this a duplicate of bug #246889 "SHA256 gives wrong answers if input
block length % 56 is 0", or is there some other issue here?
--
SHA256-HMAC debian version is not compatible with upstream package
https://bugs.launchpad.net/bugs/246889
You received this bug notification because you are a mem
Here is some debugging information:
>>> DSA.generate(161, open("/dev/urandom", "rb").read, sys.stdout.write)
p,q
4096 multiples failed
h,g
x,y
>>> DSA.generate(160, open("/dev/urandom", "rb").read, sys.stdout.write)
p,q
4096 multiples failed
4096 multiples failed
4096 multiples failed
4096 multi
his bug on my machine.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-0166
** Changed in: pycrypto
Assignee: (unassigned) => Dwayne Litzenberger (dlitz)
Status: New => Confirmed
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-0166
I am going to maintain PyCrypto. There are a lot of changes I want to
make---like deprecating RandomPool, since too many people misuse it, and
I want to set up a mailing list and a new website---so it'll take me a
while to make a release, but I'm up to the task.
--
Hash Sum mismatch
https://bugs
38 matches
Mail list logo
