search for: reissue

...SA-99:03 Security Advisory FreeBSD, Inc. Topic: Three ftp daemons in ports vulnerable to attack. Category: ports Module: wu-ftpd and proftpd Announced: 1999-09-05 Reissued: 1999-09-15 Affects: FreeBSD 3.2 (and earlier) FreeBSD-current and -stable before the correction date. Corrected: FreeBSD-3.3 RELEASE FreeBSD as of 1999/08/30 for wuftpd only (Note: there is only one ports tree which is shared with all FreeBSD branches, so if you are running a...

...GE----- ============================================================================= FreeBSD-SA-00:61 Security Advisory FreeBSD, Inc. Topic: tcpdump contains remote vulnerabilities [REISSUED] Category: core Module: tcpdump Announced: 2000-10-31 Reissued: 2000-11-06 Credits: Discovered during internal auditing. Affects: All releases of FreeBSD 3.x, 4.x prior to 4.2 FreeBSD 3.5.1-STABLE and 4.1.1-STABLE prior to the correction d...

...I worry that this defeats the return address prediction for returns in the function because calls and returns no longer are matched. Yes, this will defeat the processor's return address stack predictor. That said, I suspect it's not much of an issue on "desktop" processors: the reissue of the pop is an Atom-specific issue, so you only need to worry about the branch misprediction caused on the next return. Assuming these sequences aren't too frequent, the more elaborate tournament predictors in more powerful processors may be able to compensate for it. That said, the alterna...

...TML Warning in file(filename, "wt") : cannot open file ''C:/Users/nisabbe/Documents/@Doctoraat/R/addendum.Rcheck/00ch eck.log'': Permission denied Error in file(filename, "wt") : cannot open the connection Execution halted If, after this, I immediately reissue the R CMD check command, it works, without the error. I think this has something to do with how Win7 processes file handling (there are known issues even noticeable in windows explorer), but perhaps there is a way of circumventing this? It would be greatly appreciated, as this issue is preventing...

I noticed that we generate code like this for i386 PIC: calll L0$pb L0$pb: popl %eax movl %eax, -24(%ebp) ## 4-byte Spill I worry that this defeats the return address prediction for returns in the function because calls and returns no longer are matched. From Intel's Optimization Reference Manual: "The return address stack mechanism augments the static and dynamic

...e stores sound clips in > MP3 format, what you end up with is music that sometimes looks like > MP3. I recently bought the double-CD "Influence" remaster by The Art Of Noise and some rarer tracks were sourced from MP3 because that was all their archivist could find. Most of the reissue was direct from analogue tapes so this wasn't a quick "shovelware" reissue job. > it just has to do with the software that was used to create the music > originally. A friend of mine recorded his band's last album on DCC in the mid 1990s and released it on CD. It sounds...

...t; MP3 format, what you end up with is music that sometimes looks like >> MP3. > > I recently bought the double-CD "Influence" remaster by The Art Of > Noise > and some rarer tracks were sourced from MP3 because that was all their > archivist could find. Most of the reissue was direct from analogue > tapes > so this wasn't a quick "shovelware" reissue job. Very interesting. I've purchased many CD titles with reissued material where they clearly did not have access to anything but vinyl for some tracks. It was weird to hear the needle d...

A hiccup was reported about validating the tarball signature on some systems, so it was reissued from another workstation. Please don't worry :) Jim Klimov On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour with a few re-issues of the tag and many pushes > during the day, NUT v2.8.2 was found in a stra...

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > A hiccup was reported about validating the tarball signature on some > systems, so it was reissued from another workstation. Please don't worry :) Do you mean the signature was re-issued, which is ok, or that the tarball was re-issued, which is very much not ok(!) ?

A hiccup was reported about validating the tarball signature on some systems, so it was reissued from another workstation. Please don't worry :) Jim Klimov On Tue, Apr 2, 2024, 01:06 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour with a few re-issues of the tag and many pushes > during the day, NUT v2.8.2 was found in a stra...

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > A hiccup was reported about validating the tarball signature on some > systems, so it was reissued from another workstation. Please don't worry :) Do you mean the signature was re-issued, which is ok, or that the tarball was re-issued, which is very much not ok(!) ?

I have referred to the wiki and the RFC, but I still can't find the exact answer I'm looking for. From what I know, Dovecot uses the IMAP standard of 32 bit integers to uniquely identify messages. After a message is deleted from the mbox, can this UID ever be reissued to a new message or is that UID retired? What about after the 2 billion limit is reached? Thanks!

...kages and switch to using mozilla. For more information see RHSA-2004:429-01 Also, in order to easily identify packages which have been modified for CentOS-2, the release suffix .c2.release will be appended to the existing release. All packages which currently are missing this suffix will be reissued with the new suffix. The suffix release will always start at 1 and be incremented if a package needs to be reissues with only centos changes. When the original release is increased, the centos release will start again at 1. This is part of a new automated procedure which should result in re...

Hi, I'm attempting an one-to-one migration from courier-imap to dovecot-imap. current state: Imap-server has a self signed certificate Every client/user has a self signed client certificate that is used for SSL/TLS client authentication. All certificates are self signed "standalone" cerfificates - no CA hierarchy/structure is made. With courier-imap we could just put every

I need to disable the spin-down on an external USB drive because it spins down spontaneously while in use. The drive forgets the spindown-disable state across power outage so I need to reissue the hdparm command with each boot or hotplug. Where should I put the hdparm command to do this?

I'm receiving the following error over and over, adnauseam: Oct 1 23:59:53 NOTICE[3194]: chan_sip.c:5890 check_auth: stale nonce received from 'CNAME-CID <sip:5551212@192.168.1.X>' Does anyone know what "stale nonce" is? Thanks! Paul Conn -------------- next part -------------- An HTML attachment was scrubbed... URL:

...nd issue rsync --progress --recursive --links --stats arthur::test/ /var/tmp/haggis This copies 'test' from host 'arthur' (host A) into /var/tmp/haggis (on host B) so far so good. Everything goes to host B no problem. Next I edit a small file in 'test' on host A, then reissue the rsync command above. All files are checked and transferred according to the summary at the end. Am I incorret in assuming that only the delta of the before and after of the one small file I edited would be sent, rather than the entire directory tree defined by 'test'? Remember, I...

Hi all. We developped a pv-scsi driver that we refered Fujita-san''s scsi-driver and blkback. (see, http://www.xensource.com/files/xensummit_4/Xen_Summit_8_Matsumoto.pdf) The pv-scsi driver''s feature is as follow: * Guest has dedicated SCSI-HBAs of Dom0. * Guest can send scsi_cdb to the HBAs. * Guest recognises the HBAs from hostno of xenstore. Currentlly, We are

Attached is a prototype patch that uses CCState to lower RET nodes in the ARM target. Lowering CALL nodes will come later. This patch does not handle f64 and i64 types. For these types, it would be ideal to request the conversions below: def RetCC_ARM_APCS : CallingConv<[ CCIfType<[f32], CCBitConvertToType<i32>>, CCIfType<[f64], CCBitConvertToType<i64>>,

Hello, I use snapshot-create-as followed by blockpull when creating external snapshots of VMs. This works well, however I am curious about the behavior of blockpull after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an unexpected power loss occurs, will the VM continue to reference the backing file for the parts of it that have not yet been copied? Or, will will the disk