similar to: FreeBSD Security Advisory FreeBSD-SA-07:10.gtar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:10.gtar Security Advisory The FreeBSD Project Topic: gtar directory traversal vulnerability Category: contrib Module: contrib_tar Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

Hey folks, I looked at the man page and don't see any way to do this - maybe it is a function of the compression program used I dunno. Is there any way to get gtar to report on the compression it achieved? I can't just check file sizes because I'm writing data to tape. The basic problem is that I know how much data is there to begin with but I don't know how much room it took

Hi all, I recently used smbtar (Samba Version 2.0.4) to create a tar file "backup" of an NT filesystem. However, when using GNU tar to extract the tar file, I get a little ways into the 'tar xvpf ../file.tar' command and get a whole bunch of errors: tar: Read error on ../file.tar: Invalid argument tar: Read error on ../file.tar: Invalid argument tar: Read error on

Hello people, me again ... Just an FYI this time, I think: 0[209]1 sunray1:/contrib > gtar zxf R-1.4.1.tgz tar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar: Error exit delayed from previous errors 2[210]1 sunray1:/contrib > gtar zxvf R-1.4.1.tgz "R-1.4.1/date-stamp" R-1.4.1/date-stamp gtar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar:

Hello. I'm trying to use smbtar/smbclient (2.0.3) to copy an NTFS share on an NT Server, onto a Solaris 2.5 system. The NTFS partition is 10Gb. At the 2Gb mark, the tar stops. No errors, the file just stops. The process (smbtar) returns. Is this a problem with Solaris 2.5 ? I believe it is, and if I upgrade to 2.6, I can create larger tar files. However, does anyone know if

Hello all, I'm experiencing a most unusual problem.. I am copying a directory from one server to another (both Solaris 10/SPARC). No applications are using the directory in question on either side while the copy is in progress. After the copy successfully completes (no errors or warnings), my user brings up the application (mix of binaries, java files, and Apache Tomcat servlets) contained in

Hi folks, I've got a bit of a different scenario than I imagine most, and have spent the last 60 or 90 minutes searching Amanda list archives and googling, but did not come up with anything much. Then I went browsing around the Amanda website and found "vaulting" and was wondering whether this would suit my needs. I'm basically searching around for a backup solution and

Ref: http://blogs.sun.com/timf/entry/zfs_bootable_datasets_happily_rumbling Ref: http://mediacast.sun.com/share/timf/zfs-actual-root-install.sh This is my errata for Tim Foster''s zfs root install script: 1/ Correct mode for /tmp should be 1777. 2/ The zfs boot install should allow you to have /usr on a separate zpool: a/ We need to create /zfsroot/usr/lib in the root partition and

Hi! A (small) tar archive with files exposing an apparent LLVM optimizer bug is attached; I didn't find a way to attach files in the bugzilla interface. What's the best way to report bugs taking several files to reproduce? -- Yossi -------------- next part -------------- A non-text attachment was scrubbed... Name: bugreport.tgz Type: application/x-gtar Size: 2242 bytes Desc: not

Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Apr 27, 2015 at 2:13 PM, Joerg Schilling > <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Les Mikesell <lesmikesell at gmail.com> wrote: > > > > There was no court case, but VERITAS published a modifed version of gtar where > > additional code was added by binary only libraries from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, if deliver is started with: deliver -f sender -d user (no -a option) and no Envelope-To header exists in the mail, two problems show up in this block in main(): if (destaddr == NULL) { destaddr = deliver_get_address(mail, "Envelope-To"); if (destaddr == NULL) { destaddr = strchr(user, '@') == NULL ? user :

I have some folders with a good amount of spam. While demonstrating full text search to a user, we found a folder that would crash dovecot while doing a fts. While splitting up the mailbox to narrow it down, I found there are a good number of messages in that folder that all made it crash in the same manner. I figured I'd narrow down a single one, get that fixed, then retest the rest. I

My manifest includes this snippet class app_client_openbsd { $app_client_pkgs_obsd = [ ''glib2-2.24.1p2'', ''gtar-1.23p1'' ] package { "${app_client_pkgs_obsd}": ensure => ''installed'', source => "http://${installserver}/openbsd/${operatingsystemrelease}/packages/${hardwaremodel}/${name}.tgz", } This

I am having the following problem building R-beta_2009-10-12_r50045.tar.gz on Ubuntu 9.04 - the Jaunty Jackalope Paul ________ ... make[2]: Entering directory `/home/paul/toolchain/R/R-beta/src/library/Recommended' begin installing recommended package boot gzip: invalid option -- 'x' Try `gzip --help' for more information. tar: This does not look like a tar archive

On Mon, Apr 27, 2015 at 2:13 PM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > Les Mikesell <lesmikesell at gmail.com> wrote: > > There was no court case, but VERITAS published a modifed version of gtar where > additional code was added by binary only libraries from VERITAS. The FSF did > never try to discuss this is public even though everybody did

Hey folks, I'm reading up on gtar for tape archiving and it sounds kind of nasty and not something I really want to rely on. It looks like star from the schily tools is preferred. I'm using Centos (and RHEL) 5.7 which seems to have star but not sdd. Which leads me to believe that the Schily tools are maybe a bit "rogue" My basic requirement with what I'm doing is to use

System info: # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian squeeze/sid .. mail_plugins: readonly .. I have a requirement to have read-only to a mailbox. I have been researching through the wiki, the mailing list archives and good old Google. There was a number of similar questions with no real definitive answer. Option 1: ACL This can work, but not if the

Seems our current libarchive? That support FreeBSD's tar implementation has a bug where it can create archives it cant read back. This can be seen by simply creating an empty tar.gz file and then trying to expand or list it. In doing the above you get the following error: tar: Unrecognized archive format: Inappropriate file type or format N.B. gtar can list and expand the created file