Package: qmail-src
Version: 1.03-38
Severity: important
Dan J. Bernstein just released the code of qmail 1.03 to the public
domain. See http://cr.yp.to/qmail/dist.html for more information.
I set severity to important though the impact is to the better.
caspar
--
To UNSUBSCRIBE, email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Caspar Bothmer wrote:
| Hendrik-Jan Heins wrote:
| | But I can't reproduce the problem you had.
|
| I am not surprised. Still I have a mailbox whose very first mail got
| partially overwritten by another mail.
I just found a copy of the original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| OMFFSM, when I click on a link, that is logged on a remote server !
| That's my privacy being violated !
That's two different things, don't you think?
If I click on a link, I use that link as it is meant to be, to get
further
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Sack - Debian Bugmail wrote:
|tag 417796 wontfix
|thanks
| I would even say this isn't abug at all.
I disagree.
| You can do much more things
| with javascript.
For sure, but that is a different technique. Only because you can use
one
Package: mozilla-browser
Version: 2:1.7.8-1sarge10
Severity: important
It is possible to get information about the users' behaviour using css.
I best show it by example:
html
head
style type=text/css
#24678:hover
{
background-image:url(24678.png)
}
#22578:hover
{
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| Does it happen with iceape or epiphany/galeon/kazehakase from testing ?
I haven't tried that as I do only have sarge installs I don't want to
fiddle around with.
But if the problem is still there, the one running my demo will
Package: mozilla-browser
Version: 2:1.7.8-1sarge10
I have a list of options, one of these is selected. Under certain
conditions I want to restrict access to the values above this selected
option. I can restrict this and almost everything works well, but one
thing doesn't. I will describe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It would be great to see these bugs get some attention of the maintainers...
So I try to explain what I know about this issue:
The reason for this situation is, that apt-setup calls the system
database for the value of the key 'mirror/suite'. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frans Pop wrote:
| On Thursday 25 January 2007 13:43, Caspar Bothmer wrote:
|It would be great to see these bugs get some attention of the
|maintainers...
| As base-config has been obsoleted (it is no longer in Etch), and as this
| is not really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I feel a need to add to this bug:
| currently there is no way to fix this. So if you want decryption you
| have to allow to load remote images :( ... for now.
Recently I got a very annoying web bug contaminated newsletter.
While analyzing that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Sack wrote:
| I think I found the bug and probably fixed it :/.
Great, but what caused these problems?
| New packages (except for mozilla-firefox) are in my security
| archive. Can you please test if this update helps?
It helps, both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacek Kawa wrote:
| Caspar Bothmer wrote:
|I am not surprised. Still I have a mailbox whose very first mail got
|partially overwritten by another mail.
| Perhaps only mail index files are corrupted? Try something
| like:
No, it's the mailbox itself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| I'd like to know if you can reproduce this with your mozilla
I did some tests but I wasn't able to reproduce yet. I will do further
testing.
Maybe these data may help:
- - I mailboxes are huge (33 mailboxes, partially nested,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hendrik-Jan Heins wrote:
| But I can't reproduce the problem you had.
I am not surprised. Still I have a mailbox whose very first mail got
partially overwritten by another mail.
caspar
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| And what happens if you try this again?
I haven't tried yet.
If there is a need for it I would do further testing. Please tell me
specifically, what kind of information you want me to provide.
caspar
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Sack - Debian Bugmail wrote:
| On Thu, Dec 14, 2006 at 02:31:17PM +0100, Caspar Bothmer wrote:
|line rewritten so one can easily see this information. I first did a
|search for this pattern, removing all found messages.
| How is this done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Sack - Debian Bugmail wrote:
| Sorry for the wrong cut in my quoting ... my how is this done
| ment how do you rewrite subject of spam?
That's quite a different thing, yes :-))
I don't rewrite the subject myself. My provider changes the
Package: mozilla-mailnews
Version: 2:1.7.8-1sarge8
Severity: grave
I was cleaning up my mailbox, using Search Messages to filter for
certain patterns:
On one of my accounts mails with a certain spam level get their subject
line rewritten so one can easily see this information. I first did a
Hi,
Why don't you just set FILE_OFFSET_BITS to 64? 5.52 does recognize this
flag. Patch attached.
caspar
diff -pruN unzip-5.52.orig/debian/rules unzip-5.52/debian/rules
--- unzip-5.52.orig/debian/rules 2006-01-05 18:16:55.573032000 +0100
+++ unzip-5.52/debian/rules 2006-01-05
tags 334206 - unreproducible
thanks
Alexander Sack wrote:
On Wed, Oct 19, 2005 at 09:43:53AM +0200, Caspar Bothmer wrote:
Are there bugs posted for those issues?
While we're at it -- this bug may not be RC but it surely is reproducible...
signature.asc
Description: OpenPGP digital
I was a bit too fast... :-))
Caspar Bothmer wrote:
On Wed, Oct 19, 2005 at 09:43:53AM +0200, Caspar Bothmer wrote:
Are there bugs posted for those issues?
No. AFAIR it was fixed pretty fast in Gentoo and therefore I didn't see
a need to. And it seems to be fixed in Debian with yesterdays
Alexander Sack wrote:
true, but only for pgp/mime encrypted messages. If you inline, it
should work.
Ok, this is a viable workaround for you and me, but is it OK for
everybody? I have enough difficulties to have others sign their
messages at all...
- narrowing view via Subject or
Alexander Sack wrote:
tags 334206 + unreproducible
tags 334206 + sarge
thanks
cannot reproduce this. Maybe pressing decrypt button manually helps?
That doesn't work as the whole message is seen as containing nothing but
attachments.
I can decrypt the attachment to a browser window, select
Caspar Bothmer wrote:
I can't reproduce this error with a new account.
I did some tests and I am able to reproduce this error with a new account:
After starting mozilla mail using `mozilla --mail` I created a user
test and pulled an encrypted message from the server I sent to that
user
Alexander Sack wrote:
currently there is no way to fix this. So if you want decryption you
have to allow to load remote images :( ... for now.
This renders mozilla mail useless. Exactly this single option is
responsible for at least three broken functions:
- enigmail decryption
- narrowing
Package: mozilla-enigmail
Version: 2:0.91.4
Severity: grave
Encrypted mails get displayed as attachment which one has to save and
decrypt on the commandline. Signed mails get checked normally.
To check just send a mail to yourself using mozilla-enigmail itself.
This behaviour shows up
I was able to track this problem down to my own local configs.
I removed my old configs and now I am reconfiguring my desktop. That
is very annoying as I did quite some configuration.
BTW: I only used the tools KDE provides to configure the desktop -- no
manual changes, no third-party tools.
And again...
At this very moment I know what is causing this failure but not why it
does that.
I did rearrange the K-Menu using kmenuedit. I did some tests and I
was able to isolate one specific action. My changes included moving
/System/ to another menu.
There is no problem in moving the
tests_menuedit_cb_2005_07_18.tar.bz2
Description: BZip2 compressed data
signature.asc
Description: OpenPGP digital signature
Package: kcontrol
Version: 3.3.2-1
I configured the screensaver with kcontrol-3.3.1-4 some months ago and
everything was ok back at that time.
Some weeks ago -- a while after update to 3.3.2-1 -- I noticed that
the screensaver didn't start. When I tried to check the configs in
kcontrol, I got
Now that the freeze in sarge is really hard I
don't feel good about uploading a completely new package to the debian
archives.
It won't be a /completely/ new package, it would be the addon for
another package, namely mozilla-locale-de-at. There is just no formal
dependency on
Alexander Sack schrieb:
... that's not the way it works. They are completely different packages.
Sure, they are separate packages without any connection despite
enigmail-locale-de depending on mozilla-locale-de-at to be installed.
But this dependency doesn't change anything here.
What I meant
Caspar Bothmer schrieb:
But I think we should stop here or discuss this further privately.
One last thing -- tonight (june 03 2005) two new localisation packages
for mozilla-firefox were accepted into sarge...
caspar
signature.asc
Description: OpenPGP digital signature
Alexander Sack schrieb:
Caspar Bothmer wrote:
Your package is ready as you said. So why don't you give it a try?
For those desparately looking for a locale package, look here:
http://www.asoftsite.org/enigmail_locales.html
You didn't get my intention.
I do not *need* /your/ package to use
Alexander Sack schrieb:
Is enigmail really unusable for you or is the messages just not appropriate?
What do you mean by that?
The maintainers for mozilla-locale-de try to get their package into
sarge. It might get into sarge, it might not get into it.
As I don't install mozilla without
Markus E Leypold schrieb:
I'd be really, really thankful to the maintainers, if the localization
package found it's way into sarge. Thanks for your work, guys (and
please make it available :-).
And I join in. It's worth it.
caspar
signature.asc
Description: OpenPGP digital signature
Ok, mozilla-locale-de-at will find its way into sarge. So I will have
the following situation:
Debian could easily provide an enigmail-enhanced _and_ localized mozilla
but I have to choose between an enigmail-enhanced or a localized mozilla.
Your package is ready as you said. So why don't you
The maintainers of 'mozilla-locales-de-at' were asked -- bug #311228[1]
-- to submit an update to get it into sarge.
So my question is -- do you consider to release locales -- german
especially -- for enigmail to go into sarge as well?
I don't know how to prepare this package myself yet so I can
38 matches
Mail list logo
