https://github.com/hasse69/rar2fs

FUSE file system for reading RAR archives
https://github.com/hasse69/rar2fs

dokany freebsd fuse fuse-filesystem gplv3 linux osx solaris windows winfsp

Last synced: 7 days ago
JSON representation

FUSE file system for reading RAR archives

• Host: GitHub
• URL: https://github.com/hasse69/rar2fs
• Owner: hasse69
• License: gpl-3.0
• Created: 2011-09-02T05:58:18.000Z (about 13 years ago)
• Default Branch: master
• Last Pushed: 2024-07-04T21:12:26.000Z (4 months ago)
• Last Synced: 2024-08-02T15:23:32.641Z (3 months ago)
• Topics: dokany, freebsd, fuse, fuse-filesystem, gplv3, linux, osx, solaris, windows, winfsp
• Language: C
• Homepage: https://hasse69.github.io/rar2fs/
• Size: 923 KB
• Stars: 273
• Watchers: 25
• Forks: 26
• Open Issues: 13
• Metadata Files:
  • Readme: README
  • Changelog: ChangeLog
  • License: COPYING
  • Authors: AUTHORS

Awesome Lists containing this project

README

        
rar2fs is a FUSE based file system that can mount a source RAR archive/volume

or a directory containing any number of RAR archives and read the contents as

regular files on-the-fly. Non-archived files located in the source directory

are handled transparently. Both compressed and non-compressed 

archives/volumes are supported but full media seek support (aka. indexing) is

only available for non-compressed plaintext archives. In general support for

compressed and/or encrypted archives is "best effort", highly depending on

what type of information the archive contains and by what method it is 

accessed.

Encrypted archives are supported but since rar2fs is completely

non-interactive it requires the archive password to be stored on the local

file system in a file in plaintext format. This of course is a major security

limitation in itself. If you really need to use this feature, use it wisely.

The author(s) of rar2fs will not be held responsible for encrypted

information being exposed due to this limitation. If security is really an

issue some encryption on file system level should be considered instead.

A FUSE based encryption file system, such as encfs, has proven to work very

well together with rar2fs.