Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Install Mutt without Portage, and Why, for Air-Gappers
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Wed Oct 15, 2014 11:51 pm    Post subject: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

After doing a regular "emerge mutt", and trying to use it, I got:
Code:

ukrainian@mybox ~ $ mutt
Error in /home/ukrainian/.muttrc, line 11: ssl_usesystemcerts: unknown variable
source: errors in /home/ukrainian/.muttrc
Press any key to continue...
ukrainian@mybox ~ $


So I did:

Code:

# emerge -C mutt


(
actually you should first see more in detail this directory:

Code:

# ls -l /usr/portage/mail-client/mutt/
total 88
-rw-r--r-- 1 portage portage 56984 2014-05-15 08:31 ChangeLog
drwxr-xr-x 2 portage portage  4096 2014-03-13 22:01 files
-rw-r--r-- 1 portage portage  4409 2014-05-15 08:31 Manifest
-rw-r--r-- 1 portage portage   650 2009-10-27 22:47 metadata.xml
-rw-r--r-- 1 portage portage  8041 2014-05-14 18:31 mutt-1.5.22-r3.ebuild
-rw-r--r-- 1 portage portage  8055 2014-04-08 22:37 mutt-1.5.23-r2.ebuild
mybox ukrainian #


and if it changed, then maybe use emerge... Such as if this:

Code:

# view /usr/portage/mail-client/mutt/mutt-1.5.23-r2.ebuild
...[snip]...
    gpg?     ( >=app-crypt/gpgme-0.9.0 )
...[snip]...


is not anymore the case (and other things possibly).

Why? Because you are better of trying to use gpg-1 instead --that one above is a GUI interface, goes with the gpg-2 which you have to use gpg-agent and GUI to type password; not the mutt way really
)

The mutt in portage is the unstable of March 2014 from mutt.org, so I just checked it with the signature pointed to there. It's fine. Sure portage would not accept otherwise, but I double and triple check things often.

I will use it without the gentoo patches, however. I really don't need any GUI to type in my passwords in Mutt and other such desktop poetteringware-like stuff.

So:

Code:

# cd /usr/src
# tar xzvf /usr/portage/distfiles/mutt-1.5.23.tar.gz
# cd mutt-1.5.23/
# view INSTALL


and, after I unmounted all

Code:

# umount /<whatever-was-mounted> #proof-reading-note: '-xdev' option to find, and not needed
# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_BEFORE-PRECAUTION.txt
# ./configure --prefix=/usr 2>&1 | tee /root/mutt-1.5.23_`date +%s`_configure


This is the one I'll use for diff'ing (previous is lest I forget).
Code:

# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_BEFORE.txt
# make install 2>&1 | tee /root/mutt-1.5.23_`date +%s`_make_install
# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_AFTER.txt


Code:

# diff /root/FIND_mutt-1.5.23_1413405
FIND_mutt-1.5.23_1413405491_BEFORE.txt  FIND_mutt-1.5.23_1413405618_AFTER.txt
# diff /root/FIND_mutt-1.5.23_1413405*


shows the diff, but to get the list of files that belong to the newly
installed mutt more is needed.

This is how I got the list:

Code:

diff /root/FIND_mutt-1.5.23_1413405* | grep '> ' | sed 's/> \//\//' | egrep -v '\/proc\/|\/root\/'
/usr/share/man/man1/smime_keys.1
/usr/share/man/man1/pgpring.1
/usr/share/man/man1/flea.1
/usr/share/man/man1/pgpewrap.1
/usr/share/man/man1/muttbug.1
/usr/share/man/man1/mutt.1
/usr/share/man/man5/muttrc.5
/usr/share/man/man5/mbox.5
/usr/share/man/man5/mmdf.5
/usr/share/doc/mutt
/usr/share/doc/mutt/applying-patches.txt
/usr/share/doc/mutt/devel-notes.txt
/usr/share/doc/mutt/security.html
/usr/share/doc/mutt/INSTALL
/usr/share/doc/mutt/README.SSL
/usr/share/doc/mutt/COPYRIGHT
/usr/share/doc/mutt/samples
/usr/share/doc/mutt/samples/Mush.rc
/usr/share/doc/mutt/samples/pgp2.rc
/usr/share/doc/mutt/samples/mutt_xtitle
/usr/share/doc/mutt/samples/sample.mailcap
/usr/share/doc/mutt/samples/smime_keys_test.pl
/usr/share/doc/mutt/samples/iconv
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.6.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.6-cjk.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.1.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.irix-6.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-10.20.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-10.01.rc
/usr/share/doc/mutt/samples/iconv/iconv.osf1-4.0d.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-3.2.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.osf1-4.0a.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.4.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.5.1.rc
/usr/share/doc/mutt/samples/iconv/iconv.glibc-2.1.3.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.3.2.rc
/usr/share/doc/mutt/samples/iconv/iconv.glibc-2.1.90.rc
/usr/share/doc/mutt/samples/iconv/iconv.freebsd-3.3.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.7.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-11.00.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.2.0.rc
/usr/share/doc/mutt/samples/gpg.rc
/usr/share/doc/mutt/samples/colors.linux
/usr/share/doc/mutt/samples/sample.muttrc
/usr/share/doc/mutt/samples/ca-bundle.crt
/usr/share/doc/mutt/samples/pgp6.rc
/usr/share/doc/mutt/samples/smime.rc
/usr/share/doc/mutt/samples/sample.muttrc-tlr
/usr/share/doc/mutt/samples/colors.default
/usr/share/doc/mutt/samples/pgp5.rc
/usr/share/doc/mutt/samples/Tin.rc
/usr/share/doc/mutt/samples/Pine.rc
/usr/share/doc/mutt/PGP-Notes.txt
/usr/share/doc/mutt/ChangeLog
/usr/share/doc/mutt/smime-notes.txt
/usr/share/doc/mutt/tuning.html
/usr/share/doc/mutt/advancedusage.html
/usr/share/doc/mutt/reference.html
/usr/share/doc/mutt/configuration.html
/usr/share/doc/mutt/mimesupport.html
/usr/share/doc/mutt/manual.html
/usr/share/doc/mutt/miscellany.html
/usr/share/doc/mutt/README
/usr/share/doc/mutt/README.SECURITY
/usr/share/doc/mutt/GPL
/usr/share/doc/mutt/gettingstarted.html
/usr/share/doc/mutt/optionalfeatures.html
/usr/share/doc/mutt/TODO
/usr/share/doc/mutt/NEWS
/usr/share/doc/mutt/intro.html
/usr/share/doc/mutt/index.html
/usr/share/doc/mutt/patch-notes.txt
/usr/share/doc/mutt/manual.txt
/usr/share/locale/id/LC_MESSAGES/mutt.mo
/usr/share/locale/de/LC_MESSAGES/mutt.mo
/usr/share/locale/bg/LC_MESSAGES/mutt.mo
/usr/share/locale/it/LC_MESSAGES/mutt.mo
/usr/share/locale/lt/LC_MESSAGES/mutt.mo
/usr/share/locale/eu/LC_MESSAGES/mutt.mo
/usr/share/locale/cs/LC_MESSAGES/mutt.mo
/usr/share/locale/zh_TW/LC_MESSAGES/mutt.mo
/usr/share/locale/pl/LC_MESSAGES/mutt.mo
/usr/share/locale/tr/LC_MESSAGES/mutt.mo
/usr/share/locale/fr/LC_MESSAGES/mutt.mo
/usr/share/locale/nl/LC_MESSAGES/mutt.mo
/usr/share/locale/ko/LC_MESSAGES/mutt.mo
/usr/share/locale/ga/LC_MESSAGES/mutt.mo
/usr/share/locale/et/LC_MESSAGES/mutt.mo
/usr/share/locale/ca/LC_MESSAGES/mutt.mo
/usr/share/locale/zh_CN/LC_MESSAGES/mutt.mo
/usr/share/locale/gl/LC_MESSAGES/mutt.mo
/usr/share/locale/uk/LC_MESSAGES/mutt.mo
/usr/share/locale/ru/LC_MESSAGES/mutt.mo
/usr/share/locale/sv/LC_MESSAGES/mutt.mo
/usr/share/locale/hu/LC_MESSAGES/mutt.mo
/usr/share/locale/sk/LC_MESSAGES/mutt.mo
/usr/share/locale/pt_BR/LC_MESSAGES/mutt.mo
/usr/share/locale/el/LC_MESSAGES/mutt.mo
/usr/share/locale/ja/LC_MESSAGES/mutt.mo
/usr/share/locale/es/LC_MESSAGES/mutt.mo
/usr/share/locale/da/LC_MESSAGES/mutt.mo
/usr/share/locale/eo/LC_MESSAGES/mutt.mo
/usr/bin/mutt
/usr/bin/pgpring
/usr/bin/flea
/usr/bin/smime_keys
/usr/bin/muttbug
/usr/bin/pgpewrap
/usr/src/mutt-1.5.23/rfc1524.o
/usr/src/mutt-1.5.23/score.o
/usr/src/mutt-1.5.23/pgp.o
/usr/src/mutt-1.5.23/cryptglue.o
/usr/src/mutt-1.5.23/curs_main.o
/usr/src/mutt-1.5.23/mbox.o
/usr/src/mutt-1.5.23/crypt-mod.o
/usr/src/mutt-1.5.23/parse.o
/usr/src/mutt-1.5.23/pgpewrap.o
/usr/src/mutt-1.5.23/crypt.o
/usr/src/mutt-1.5.23/crypt-mod-pgp-classic.o
/usr/src/mutt-1.5.23/getdomain.o
/usr/src/mutt-1.5.23/resize.o
/usr/src/mutt-1.5.23/pgpkey.o
/usr/src/mutt-1.5.23/pgpmicalg.o
/usr/src/mutt-1.5.23/mutt
/usr/src/mutt-1.5.23/handler.o
/usr/src/mutt-1.5.23/pgpring
/usr/src/mutt-1.5.23/dotlock.o
/usr/src/mutt-1.5.23/enter.o
/usr/src/mutt-1.5.23/mbyte.o
/usr/src/mutt-1.5.23/history.o
/usr/src/mutt-1.5.23/conststrings.o
/usr/src/mutt-1.5.23/patchlist.c
/usr/src/mutt-1.5.23/charset.o
/usr/src/mutt-1.5.23/hash.o
/usr/src/mutt-1.5.23/sort.o
/usr/src/mutt-1.5.23/commands.o
/usr/src/mutt-1.5.23/mh.o
/usr/src/mutt-1.5.23/ascii.o
/usr/src/mutt-1.5.23/pager.o
/usr/src/mutt-1.5.23/compose.o
/usr/src/mutt-1.5.23/txt2c
/usr/src/mutt-1.5.23/flags.o
/usr/src/mutt-1.5.23/gnupgparse.o
/usr/src/mutt-1.5.23/menu.o
/usr/src/mutt-1.5.23/pgppubring.o
/usr/src/mutt-1.5.23/addrbook.o
/usr/src/mutt-1.5.23/crypt-mod-smime-classic.o
/usr/src/mutt-1.5.23/alias.o
/usr/src/mutt-1.5.23/complete.o
/usr/src/mutt-1.5.23/lib.o
/usr/src/mutt-1.5.23/keymap.o
/usr/src/mutt-1.5.23/send.o
/usr/src/mutt-1.5.23/hdrline.o
/usr/src/mutt-1.5.23/sendlib.o
/usr/src/mutt-1.5.23/postpone.o
/usr/src/mutt-1.5.23/status.o
/usr/src/mutt-1.5.23/patchlist.o
/usr/src/mutt-1.5.23/group.o
/usr/src/mutt-1.5.23/browser.o
/usr/src/mutt-1.5.23/url.o
/usr/src/mutt-1.5.23/pgppacket.o
/usr/src/mutt-1.5.23/muttlib.o
/usr/src/mutt-1.5.23/help.o
/usr/src/mutt-1.5.23/mx.o
/usr/src/mutt-1.5.23/reldate.h
/usr/src/mutt-1.5.23/flea
/usr/src/mutt-1.5.23/from.o
/usr/src/mutt-1.5.23/md5.o
/usr/src/mutt-1.5.23/sha1.o
/usr/src/mutt-1.5.23/recvcmd.o
/usr/src/mutt-1.5.23/extlib.o
/usr/src/mutt-1.5.23/copy.o
/usr/src/mutt-1.5.23/system.o
/usr/src/mutt-1.5.23/thread.o
/usr/src/mutt-1.5.23/filter.o
/usr/src/mutt-1.5.23/rfc2047.o
/usr/src/mutt-1.5.23/main.o
/usr/src/mutt-1.5.23/hook.o
/usr/src/mutt-1.5.23/headers.o
/usr/src/mutt-1.5.23/pattern.o
/usr/src/mutt-1.5.23/doc/smime_keys.1
/usr/src/mutt-1.5.23/doc/makedoc
/usr/src/mutt-1.5.23/doc/muttrc.man
/usr/src/mutt-1.5.23/doc/instdoc
/usr/src/mutt-1.5.23/doc/pgpring.1
/usr/src/mutt-1.5.23/doc/makedoc.o
/usr/src/mutt-1.5.23/doc/pgpewrap.1
/usr/src/mutt-1.5.23/doc/mutt.1
/usr/src/mutt-1.5.23/doc/manual.xml
/usr/src/mutt-1.5.23/edit.o
/usr/src/mutt-1.5.23/smime.o
/usr/src/mutt-1.5.23/rfc2231.o
/usr/src/mutt-1.5.23/attach.o
/usr/src/mutt-1.5.23/curs_lib.o
/usr/src/mutt-1.5.23/init.o
/usr/src/mutt-1.5.23/date.o
/usr/src/mutt-1.5.23/color.o
/usr/src/mutt-1.5.23/base64.o
/usr/src/mutt-1.5.23/pgplib.o
/usr/src/mutt-1.5.23/recvattach.o
/usr/src/mutt-1.5.23/rfc822.o
/usr/src/mutt-1.5.23/editmsg.o
/usr/src/mutt-1.5.23/query.o
/usr/src/mutt-1.5.23/smime_keys
/usr/src/mutt-1.5.23/safe_asprintf.o
/usr/src/mutt-1.5.23/rfc3676.o
/usr/src/mutt-1.5.23/mutt_idna.o
/usr/src/mutt-1.5.23/buffy.o
/usr/src/mutt-1.5.23/pgpinvoke.o
/usr/src/mutt-1.5.23/signal.o
/usr/src/mutt-1.5.23/keymap_defs.h
/usr/src/mutt-1.5.23/conststrings.c
/usr/src/mutt-1.5.23/pgpewrap
/usr/etc
/usr/etc/mime.types.dist
/usr/etc/mime.types
/usr/etc/Muttrc.dist
/usr/etc/Muttrc


Sure enough, I really need to do:

Code:

diff /root/FIND_mutt-1.5.23_1413405* | grep '> ' | sed 's/> \//\//' | egrep -v '\/proc\/|\/root\/' > /root/mutt-1.5.23_`date +%s`_FILES


to stow that in a file (and stow it somewhere more appropriate than /root. This way or some othe, but some way is surely needed in case you want to remove these some day. Portage keeps no track whatsoever of files installed this way.

I just stow away three files:

Code:

# ls -ltr /root/mutt-1.5.23_141340*
-rw-r--r-- 1 root root 10802 2014-10-15 22:35 /root/mutt-1.5.23_1413405295_configure
-rw-r--r-- 1 root root 44661 2014-10-15 22:40 /root/mutt-1.5.23_1413405572_make_install
-rw-r--r-- 1 root root  7490 2014-10-15 22:53 /root/mutt-1.5.23_1413406411_FILES


of which the last one (..._FILES) is the most important to have, if I want to remove the package.

Actually I just need it, because judging by not being advisory to give the portage's mutt the gpg flag (and get the whole GUI silly --for security aware people-- stuff for gpg), I now see that I, with the source compilation should have followed different route regarding ssl, another thing I use FOSS Linux for. I can't log into my dovecot server because no ssl support...

I know that because on trying to launch mutt I got these errors:

Code:

$ mutt
Error in /home/ukrainian/.muttrc, line 8: ssl_starttls: unknown variable
Error in /home/ukrainian/.muttrc, line 9: ssl_force_tls: unknown variable
Error in /home/ukrainian/.muttrc, line 10: ssl_force_tls: unknown variable
Error in /home/ukrainian/.muttrc, line 11: ssl_usesystemcerts: unknown variable
Error in /home/ukrainian/.muttrc, line 12: imap_passive: unknown variable
source: errors in /home/ukrainian/.muttrc
$


(I'm not Ukrainian, but Croat, a related nation, but I support Ukrainians and wish Russians to be humane and leave other people's lands alone.)

So:

Code:

for i in `cat /root/mutt-1.5.23_1413406411_FILES`; do ls -ld $i ; read FAKE ; done ;


as I first want to see all the files to uninstall scroll before me, and stop for closer look if I decide.

"read FAKE" is for you to press Enter to go on, or keep pressed for it to go all the way.

Now the first run:

Code:

for i in `cat /root/mutt-1.5.23_1413406411_FILES`; do if [ -f "$i" ] ; then rm -v $i ; fi ; done ;



That removed files. And the second run:

Code:

for i in `cat /root/mutt-1.5.23_1413406411_FILES`; do if [ -d "$i" ] ; then rmdir -v $i ; fi ; done ;


And that removed directories.

And I can start over (I have to, unfortunately, because I need the ssl flag of the mutt configure) with system not dirtied with files not-known neither by portage nor by me which would have been the case had I not had logged what I was installing.

This must work fine:

Code:

 ./configure --prefix=/usr --with-homespool=Maildir --enable-pop -enable-imap --with-ssl --with-gnutls --with-sasl 2>&1 | tee /root/mutt-1.5.23_`date +%s


And I repeated the other steps.

Code:

mybox mutt-1.5.23 # diff /root/mutt-1.5.23_*_FILES
mutt-1.5.23_1413406411_FILES  mutt-1.5.23_1413408034_FILES 
mybox mutt-1.5.23 # diff /root/mutt-1.5.23_*_FILES

143
> /usr/src/mutt-1.5.23/pop_auth.o
144a146
> /usr/src/mutt-1.5.23/pop.o
151a154
> /usr/src/mutt-1.5.23/mutt_ssl.o
166a170
> /usr/src/mutt-1.5.23/pop_lib.o
167a172
> /usr/src/mutt-1.5.23/account.o
191a197
> /usr/src/mutt-1.5.23/mutt_tunnel.o
192a199
> /usr/src/mutt-1.5.23/mutt_socket.o
202a210
> /usr/src/mutt-1.5.23/bcache.o
211a220,229
> /usr/src/mutt-1.5.23/imap/util.o
> /usr/src/mutt-1.5.23/imap/message.o
> /usr/src/mutt-1.5.23/imap/auth_sasl.o
> /usr/src/mutt-1.5.23/imap/imap.o
> /usr/src/mutt-1.5.23/imap/auth_login.o
> /usr/src/mutt-1.5.23/imap/libimap.a
> /usr/src/mutt-1.5.23/imap/command.o
> /usr/src/mutt-1.5.23/imap/browse.o
> /usr/src/mutt-1.5.23/imap/auth.o
> /usr/src/mutt-1.5.23/imap/utf7.o
212a231
> /usr/src/mutt-1.5.23/mutt_sasl.o


That is the diff btwn the previous, deleted and this install, which is to stay.

And, upon:

Code:

$ mutt # That is "$", meaning as regular user, not anymore root


I get this page (well I also have other things set up, but no time to explain)

Code:

q:Exit  ?:Help
This certificate belongs to:
   gitb-ukrainian
   Unknown
   Croatia Fidelis
   Officium Centralis
   Zagreb

This certificate was issued by:
   gitb-ukrainian
   Unknown
   Croatia Fidelis
   Officium Centralis
   Zagreb

This certificate is valid
   from Aug 29 08:52:03 2014 GMT
     to Aug 29 08:52:03 2015 GMT

Fingerprint: 071A 2DC0 F91C 7E76 0020 BDEF 948B E119

...[snip]...

-- Mutt: SSL Certificate check (certificate 0 of 0 in chain)
(r)eject, accept (o)nce, (a)ccept always


only nicer that I can describe here.

Now at least two reasons why I didn't file a bug for the error in portage's
current mutt package.

I'm not yet very familiar with reporting bugs, but that's half a reason, To
make it complete first reason, I work far too slowly to find time for it.

On the other side, I do understand that this is the better way to install mutt
currently, for people who tend to like air-gapping, and there are many of such
people (amoong whom I belong), ending up on Gentoo, as the last bastion of
still some-scale free computing (potteringware is not, as M$ and apple is
not), it is simply wrong to add all those GUIs for just gnupg to have
passwords. I wrote about it:

Air-Gapped Gentoo Install, Tentative
http://forums.gentoo.org/viewtopic-t-987268-start-25.html#7551458

( and a little more on what I chose for my mail setup is one of the issues here:

Postfix smtp-tls-wrapper, Bkp/Cloning Mthd, A Zerk Provider
http://forums.gentoo.org/viewtopic-t-999436.html
)


and since it's mainstream, it would be much more work talking maintainers to
do it than to tell people how to do it the right way (as air-gappers like me
consider it to be). That is the second reason.

I just tried and sent a note that I posted this tip on Gentoo Forums to ago (Agostino Sarubbo, in charge of mutt in Gentoo, and to grobian, Fabian Groffen). Maybe that should go some way for the devs.
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
Back to top
View user's profile Send private message
Ant P.
Advocate
Advocate


Joined: 18 Apr 2009
Posts: 2413
Location: UK

PostPosted: Thu Oct 16, 2014 12:25 am    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

miroR wrote:
After doing a regular "emerge mutt", and trying to use it, I got:
Code:

ukrainian@mybox ~ $ mutt
Error in /home/ukrainian/.muttrc, line 11: ssl_usesystemcerts: unknown variable
source: errors in /home/ukrainian/.muttrc
Press any key to continue...
ukrainian@mybox ~ $


So I did:

Code:

# emerge -C mutt

So instead of paying attention to the output of emerge, or trying to actually diagnose the problem, your first reaction is to panic, rip it out and compile it by hand. Just a cargo-cult, ricer, knee-jerk reaction. Okay.

Quote:
(
actually you should first see more in detail this directory:

Code:

# ls -l /usr/portage/mail-client/mutt/
total 88
-rw-r--r-- 1 portage portage 56984 2014-05-15 08:31 ChangeLog
drwxr-xr-x 2 portage portage  4096 2014-03-13 22:01 files
-rw-r--r-- 1 portage portage  4409 2014-05-15 08:31 Manifest
-rw-r--r-- 1 portage portage   650 2009-10-27 22:47 metadata.xml
-rw-r--r-- 1 portage portage  8041 2014-05-14 18:31 mutt-1.5.22-r3.ebuild
-rw-r--r-- 1 portage portage  8055 2014-04-08 22:37 mutt-1.5.23-r2.ebuild
mybox ukrainian #


and if it changed, then maybe use emerge...

What a waste of CPU time.

Quote:
Such as if this:

Code:

# view /usr/portage/mail-client/mutt/mutt-1.5.23-r2.ebuild
...[snip]...
    gpg?     ( >=app-crypt/gpgme-0.9.0 )
...[snip]...


is not anymore the case (and other things possibly).

Why? Because you are better of trying to use gpg-1 instead --that one above is a GUI interface, goes with the gpg-2 which you have to use gpg-agent and GUI to type password; not the mutt way really
)

The mutt in portage is the unstable of March 2014 from mutt.org, so I just checked it with the signature pointed to there. It's fine. Sure portage would not accept otherwise, but I double and triple check things often.

I will use it without the gentoo patches, however. I really don't need any GUI to type in my passwords in Mutt and other such desktop poetteringware-like stuff.

Or you could use `eselect pinentry ncurses` instead of screaming about "poetteringware" like a raving lunatic. God forbid you actually learn to use the damn software you're running!

Quote:
So:

Code:

# cd /usr/src
# tar xzvf /usr/portage/distfiles/mutt-1.5.23.tar.gz
# cd mutt-1.5.23/
# view INSTALL


and, after I unmounted all

Code:

# umount /<whatever-was-mounted> #proof-reading-note: '-xdev' option to find, and not needed
# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_BEFORE-PRECAUTION.txt
# ./configure --prefix=/usr 2>&1 | tee /root/mutt-1.5.23_`date +%s`_configure


This is the one I'll use for diff'ing (previous is lest I forget).
Code:

# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_BEFORE.txt
# make install 2>&1 | tee /root/mutt-1.5.23_`date +%s`_make_install
# find / -name '*' > /root/FIND_mutt-1.5.23_`date +%s`_AFTER.txt


Code:

# diff /root/FIND_mutt-1.5.23_1413405
FIND_mutt-1.5.23_1413405491_BEFORE.txt  FIND_mutt-1.5.23_1413405618_AFTER.txt
# diff /root/FIND_mutt-1.5.23_1413405*


shows the diff, but to get the list of files that belong to the newly
installed mutt more is needed.

This is how I got the list:

Code:

diff /root/FIND_mutt-1.5.23_1413405* | grep '> ' | sed 's/> \//\//' | egrep -v '\/proc\/|\/root\/'
/usr/share/man/man1/smime_keys.1
/usr/share/man/man1/pgpring.1
/usr/share/man/man1/flea.1
/usr/share/man/man1/pgpewrap.1
/usr/share/man/man1/muttbug.1
/usr/share/man/man1/mutt.1
/usr/share/man/man5/muttrc.5
/usr/share/man/man5/mbox.5
/usr/share/man/man5/mmdf.5
/usr/share/doc/mutt
/usr/share/doc/mutt/applying-patches.txt
/usr/share/doc/mutt/devel-notes.txt
/usr/share/doc/mutt/security.html
/usr/share/doc/mutt/INSTALL
/usr/share/doc/mutt/README.SSL
/usr/share/doc/mutt/COPYRIGHT
/usr/share/doc/mutt/samples
/usr/share/doc/mutt/samples/Mush.rc
/usr/share/doc/mutt/samples/pgp2.rc
/usr/share/doc/mutt/samples/mutt_xtitle
/usr/share/doc/mutt/samples/sample.mailcap
/usr/share/doc/mutt/samples/smime_keys_test.pl
/usr/share/doc/mutt/samples/iconv
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.6.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.6-cjk.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.1.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.irix-6.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-10.20.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-10.01.rc
/usr/share/doc/mutt/samples/iconv/iconv.osf1-4.0d.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-3.2.5.rc
/usr/share/doc/mutt/samples/iconv/iconv.osf1-4.0a.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.4.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.5.1.rc
/usr/share/doc/mutt/samples/iconv/iconv.glibc-2.1.3.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.3.2.rc
/usr/share/doc/mutt/samples/iconv/iconv.glibc-2.1.90.rc
/usr/share/doc/mutt/samples/iconv/iconv.freebsd-3.3.rc
/usr/share/doc/mutt/samples/iconv/iconv.solaris-2.7.rc
/usr/share/doc/mutt/samples/iconv/iconv.hpux-11.00.rc
/usr/share/doc/mutt/samples/iconv/iconv.aix-4.2.0.rc
/usr/share/doc/mutt/samples/gpg.rc
/usr/share/doc/mutt/samples/colors.linux
/usr/share/doc/mutt/samples/sample.muttrc
/usr/share/doc/mutt/samples/ca-bundle.crt
/usr/share/doc/mutt/samples/pgp6.rc
/usr/share/doc/mutt/samples/smime.rc
/usr/share/doc/mutt/samples/sample.muttrc-tlr
/usr/share/doc/mutt/samples/colors.default
/usr/share/doc/mutt/samples/pgp5.rc
/usr/share/doc/mutt/samples/Tin.rc
/usr/share/doc/mutt/samples/Pine.rc
/usr/share/doc/mutt/PGP-Notes.txt
/usr/share/doc/mutt/ChangeLog
/usr/share/doc/mutt/smime-notes.txt
/usr/share/doc/mutt/tuning.html
/usr/share/doc/mutt/advancedusage.html
/usr/share/doc/mutt/reference.html
/usr/share/doc/mutt/configuration.html
/usr/share/doc/mutt/mimesupport.html
/usr/share/doc/mutt/manual.html
/usr/share/doc/mutt/miscellany.html
/usr/share/doc/mutt/README
/usr/share/doc/mutt/README.SECURITY
/usr/share/doc/mutt/GPL
/usr/share/doc/mutt/gettingstarted.html
/usr/share/doc/mutt/optionalfeatures.html
/usr/share/doc/mutt/TODO
/usr/share/doc/mutt/NEWS
/usr/share/doc/mutt/intro.html
/usr/share/doc/mutt/index.html
/usr/share/doc/mutt/patch-notes.txt
/usr/share/doc/mutt/manual.txt
/usr/share/locale/id/LC_MESSAGES/mutt.mo
/usr/share/locale/de/LC_MESSAGES/mutt.mo
/usr/share/locale/bg/LC_MESSAGES/mutt.mo
/usr/share/locale/it/LC_MESSAGES/mutt.mo
/usr/share/locale/lt/LC_MESSAGES/mutt.mo
/usr/share/locale/eu/LC_MESSAGES/mutt.mo
/usr/share/locale/cs/LC_MESSAGES/mutt.mo
/usr/share/locale/zh_TW/LC_MESSAGES/mutt.mo
/usr/share/locale/pl/LC_MESSAGES/mutt.mo
/usr/share/locale/tr/LC_MESSAGES/mutt.mo
/usr/share/locale/fr/LC_MESSAGES/mutt.mo
/usr/share/locale/nl/LC_MESSAGES/mutt.mo
/usr/share/locale/ko/LC_MESSAGES/mutt.mo
/usr/share/locale/ga/LC_MESSAGES/mutt.mo
/usr/share/locale/et/LC_MESSAGES/mutt.mo
/usr/share/locale/ca/LC_MESSAGES/mutt.mo
/usr/share/locale/zh_CN/LC_MESSAGES/mutt.mo
/usr/share/locale/gl/LC_MESSAGES/mutt.mo
/usr/share/locale/uk/LC_MESSAGES/mutt.mo
/usr/share/locale/ru/LC_MESSAGES/mutt.mo
/usr/share/locale/sv/LC_MESSAGES/mutt.mo
/usr/share/locale/hu/LC_MESSAGES/mutt.mo
/usr/share/locale/sk/LC_MESSAGES/mutt.mo
/usr/share/locale/pt_BR/LC_MESSAGES/mutt.mo
/usr/share/locale/el/LC_MESSAGES/mutt.mo
/usr/share/locale/ja/LC_MESSAGES/mutt.mo
/usr/share/locale/es/LC_MESSAGES/mutt.mo
/usr/share/locale/da/LC_MESSAGES/mutt.mo
/usr/share/locale/eo/LC_MESSAGES/mutt.mo
/usr/bin/mutt
/usr/bin/pgpring
/usr/bin/flea
/usr/bin/smime_keys
/usr/bin/muttbug
/usr/bin/pgpewrap
/usr/src/mutt-1.5.23/rfc1524.o
/usr/src/mutt-1.5.23/score.o
/usr/src/mutt-1.5.23/pgp.o
/usr/src/mutt-1.5.23/cryptglue.o
/usr/src/mutt-1.5.23/curs_main.o
/usr/src/mutt-1.5.23/mbox.o
/usr/src/mutt-1.5.23/crypt-mod.o
/usr/src/mutt-1.5.23/parse.o
/usr/src/mutt-1.5.23/pgpewrap.o
/usr/src/mutt-1.5.23/crypt.o
/usr/src/mutt-1.5.23/crypt-mod-pgp-classic.o
/usr/src/mutt-1.5.23/getdomain.o
/usr/src/mutt-1.5.23/resize.o
/usr/src/mutt-1.5.23/pgpkey.o
/usr/src/mutt-1.5.23/pgpmicalg.o
/usr/src/mutt-1.5.23/mutt
/usr/src/mutt-1.5.23/handler.o
/usr/src/mutt-1.5.23/pgpring
/usr/src/mutt-1.5.23/dotlock.o
/usr/src/mutt-1.5.23/enter.o
/usr/src/mutt-1.5.23/mbyte.o
/usr/src/mutt-1.5.23/history.o
/usr/src/mutt-1.5.23/conststrings.o
/usr/src/mutt-1.5.23/patchlist.c
/usr/src/mutt-1.5.23/charset.o
/usr/src/mutt-1.5.23/hash.o
/usr/src/mutt-1.5.23/sort.o
/usr/src/mutt-1.5.23/commands.o
/usr/src/mutt-1.5.23/mh.o
/usr/src/mutt-1.5.23/ascii.o
/usr/src/mutt-1.5.23/pager.o
/usr/src/mutt-1.5.23/compose.o
/usr/src/mutt-1.5.23/txt2c
/usr/src/mutt-1.5.23/flags.o
/usr/src/mutt-1.5.23/gnupgparse.o
/usr/src/mutt-1.5.23/menu.o
/usr/src/mutt-1.5.23/pgppubring.o
/usr/src/mutt-1.5.23/addrbook.o
/usr/src/mutt-1.5.23/crypt-mod-smime-classic.o
/usr/src/mutt-1.5.23/alias.o
/usr/src/mutt-1.5.23/complete.o
/usr/src/mutt-1.5.23/lib.o
/usr/src/mutt-1.5.23/keymap.o
/usr/src/mutt-1.5.23/send.o
/usr/src/mutt-1.5.23/hdrline.o
/usr/src/mutt-1.5.23/sendlib.o
/usr/src/mutt-1.5.23/postpone.o
/usr/src/mutt-1.5.23/status.o
/usr/src/mutt-1.5.23/patchlist.o
/usr/src/mutt-1.5.23/group.o
/usr/src/mutt-1.5.23/browser.o
/usr/src/mutt-1.5.23/url.o
/usr/src/mutt-1.5.23/pgppacket.o
/usr/src/mutt-1.5.23/muttlib.o
/usr/src/mutt-1.5.23/help.o
/usr/src/mutt-1.5.23/mx.o
/usr/src/mutt-1.5.23/reldate.h
/usr/src/mutt-1.5.23/flea
/usr/src/mutt-1.5.23/from.o
/usr/src/mutt-1.5.23/md5.o
/usr/src/mutt-1.5.23/sha1.o
/usr/src/mutt-1.5.23/recvcmd.o
/usr/src/mutt-1.5.23/extlib.o
/usr/src/mutt-1.5.23/copy.o
/usr/src/mutt-1.5.23/system.o
/usr/src/mutt-1.5.23/thread.o
/usr/src/mutt-1.5.23/filter.o
/usr/src/mutt-1.5.23/rfc2047.o
/usr/src/mutt-1.5.23/main.o
/usr/src/mutt-1.5.23/hook.o
/usr/src/mutt-1.5.23/headers.o
/usr/src/mutt-1.5.23/pattern.o
/usr/src/mutt-1.5.23/doc/smime_keys.1
/usr/src/mutt-1.5.23/doc/makedoc
/usr/src/mutt-1.5.23/doc/muttrc.man
/usr/src/mutt-1.5.23/doc/instdoc
/usr/src/mutt-1.5.23/doc/pgpring.1
/usr/src/mutt-1.5.23/doc/makedoc.o
/usr/src/mutt-1.5.23/doc/pgpewrap.1
/usr/src/mutt-1.5.23/doc/mutt.1
/usr/src/mutt-1.5.23/doc/manual.xml
/usr/src/mutt-1.5.23/edit.o
/usr/src/mutt-1.5.23/smime.o
/usr/src/mutt-1.5.23/rfc2231.o
/usr/src/mutt-1.5.23/attach.o
/usr/src/mutt-1.5.23/curs_lib.o
/usr/src/mutt-1.5.23/init.o
/usr/src/mutt-1.5.23/date.o
/usr/src/mutt-1.5.23/color.o
/usr/src/mutt-1.5.23/base64.o
/usr/src/mutt-1.5.23/pgplib.o
/usr/src/mutt-1.5.23/recvattach.o
/usr/src/mutt-1.5.23/rfc822.o
/usr/src/mutt-1.5.23/editmsg.o
/usr/src/mutt-1.5.23/query.o
/usr/src/mutt-1.5.23/smime_keys
/usr/src/mutt-1.5.23/safe_asprintf.o
/usr/src/mutt-1.5.23/rfc3676.o
/usr/src/mutt-1.5.23/mutt_idna.o
/usr/src/mutt-1.5.23/buffy.o
/usr/src/mutt-1.5.23/pgpinvoke.o
/usr/src/mutt-1.5.23/signal.o
/usr/src/mutt-1.5.23/keymap_defs.h
/usr/src/mutt-1.5.23/conststrings.c
/usr/src/mutt-1.5.23/pgpewrap
/usr/etc
/usr/etc/mime.types.dist
/usr/etc/mime.types
/usr/etc/Muttrc.dist
/usr/etc/Muttrc


Sure enough, I really need to do:

Code:

diff /root/FIND_mutt-1.5.23_1413405* | grep '> ' | sed 's/> \//\//' | egrep -v '\/proc\/|\/root\/' > /root/mutt-1.5.23_`date +%s`_FILES


to stow that in a file (and stow it somewhere more appropriate than /root. This way or some othe, but some way is surely needed in case you want to remove these some day. Portage keeps no track whatsoever of files installed this way.

This is fucking ridiculous. Not only that, you're flat out wrong and didn't RTFM at any point. /var/db/pkg/*/*/CONTENTS

Quote:
I just stow away three files:

Code:

# ls -ltr /root/mutt-1.5.23_141340*
-rw-r--r-- 1 root root 10802 2014-10-15 22:35 /root/mutt-1.5.23_1413405295_configure
-rw-r--r-- 1 root root 44661 2014-10-15 22:40 /root/mutt-1.5.23_1413405572_make_install
-rw-r--r-- 1 root root  7490 2014-10-15 22:53 /root/mutt-1.5.23_1413406411_FILES


of which the last one (..._FILES) is the most important to have, if I want to remove the package.

And how do you think portage knows which files emerge -C should remove? /dev/random?

Quote:
Actually I just need it, because judging by not being advisory to give the portage's mutt the gpg flag (and get the whole GUI silly --for security aware people-- stuff for gpg), I now see that I, with the source compilation should have followed different route regarding ssl, another thing I use FOSS Linux for. I can't log into my dovecot server because no ssl support...

I know that because on trying to launch mutt I got these errors:

Code:

$ mutt
Error in /home/ukrainian/.muttrc, line 8: ssl_starttls: unknown variable
Error in /home/ukrainian/.muttrc, line 9: ssl_force_tls: unknown variable
Error in /home/ukrainian/.muttrc, line 10: ssl_force_tls: unknown variable
Error in /home/ukrainian/.muttrc, line 11: ssl_usesystemcerts: unknown variable
Error in /home/ukrainian/.muttrc, line 12: imap_passive: unknown variable
source: errors in /home/ukrainian/.muttrc
$

So after all that, your insane shotgun debugging approach screwed up your system even worse than it was to begin with! Bravo.

And you have the nerve to put this crap under Documentation?!

I'm not even going to bother rebuking any of the parts after that, it descended into outright political trolling.

Stop flooding our forums with this inane crap ffs. You don't need technical help, you need psychiatric help.
_________________
runit-init howto | Overlay
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2730
Location: The Peanut Gallery

PostPosted: Thu Oct 16, 2014 3:44 am    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

Ant P. wrote:
This is fucking ridiculous.

I agree; WTF is wrong with you? Why are you quoting massive stacks of file output?

And stop swearing so directly; you're not in OTW.
Quote:
Stop flooding our forums with this inane crap ffs. You don't need technical help, you need psychiatric help.

This goes too far as well, imo; I heartily concur that miror has not found the right length for his posts yet.

But hopefully he'll get better over time.

What's your excuse?
Back to top
View user's profile Send private message
i92guboj
Moderator
Moderator


Joined: 30 Nov 2004
Posts: 10040
Location: Córdoba (Spain)

PostPosted: Thu Oct 16, 2014 7:57 am    Post subject: Reply with quote

As someone said, this is not GC nor it is OTW, so we won't tolerate any direct attacks of any kind here (not that they should be tolerated in OTW either, anyway). This is a support forum, not a place for name calling and/or witch hunting.

If you have any technical arguments against a how-to that's posted here just express them in a civil manner so that people around are aware of the downsides of procedure posted by the OP.

If you think the OP is either lying or doing something that violates any forum policy, please, just report it.
_________________
Gentoo Handbook | My website
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Fri Oct 24, 2014 6:08 pm    Post subject: Reply with quote

I just niow read all the three posts above. I need time to see which of them need my reply, and what I will be able to reply.
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Sat Oct 25, 2014 3:05 am    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

Ant P. wrote:
...
Or you could use `eselect pinentry ncurses` instead...
...

No, the point is, thanks to khayyam, as can be read in some of the links pointed to in this tip, who fixed it, there is gnupg-1 in portage.
Mutt should be fine with gnupg-1 without stupid frills.
And I thanked khayyam for fixing it back then; since I really want a gnupg that doesn't need assistance to just read a password. That is unreasonable to force on users.

Ant P. wrote:
...
Not only that, you're flat out wrong and didn't RTFM at any point. /var/db/pkg/*/*/CONTENTS
...

I see. It is there to be found. Reading so much all the time, Missed that info somewhere.

Thanks for warning the fellow, steveL and i92guboj!
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Sat Oct 25, 2014 3:42 am    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

miroR wrote:
Ant P. wrote:
...
Not only that, you're flat out wrong and didn't RTFM at any point. /var/db/pkg/*/*/CONTENTS
...

I see. It is there to be found. Reading so much all the time, Missed that info somewhere.
...

Hey, I may have not known before about that database in /var, but the tip is still just fine and completely correct!

Because that database holds only what portage installs. And I don't see another way to check on what's installed than what I suggested, apart from, sure, safekeeping the 'make install''s log.

Because it is all in make install's STDOUT, and only needs to be kept. Portage will never know about it.

Surely the best thing is if the Mutt maintainers decide to keep with what Michael Elkins, the Mutt Dude, preaches, and not the, sorry to have to say, GUI crap on top of Mutt just for the sake of reading a password from user. That is crap!

And that is why I sent the mail to two of the Mutt maintainers.
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2730
Location: The Peanut Gallery

PostPosted: Sat Oct 25, 2014 2:40 pm    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

miroR wrote:
I may have not known before about that database in /var, but the tip is still just fine and completely correct!

Because that database holds only what portage installs. And I don't see another way to check on what's installed than what I suggested, apart from, sure, safekeeping the 'make install''s log.

Because it is all in make install's STDOUT, and only needs to be kept. Portage will never know about it.

This doesn't make sense to me, as it's based on a misconception. The point is that portage will install whatever the makefile installs to DESTDIR (which is a root image.)

The most that you'd have to "worry" about is the ebuild doing something customised for Gentoo. And that's all transparently in front of you in the ebuild. Hell you can just -r bump it and rework it if you want, so it's hardly obfuscated.

So, I'm not sure what problem you're trying to solve by acting as if portage is an untrusted black box, instead of just building on top of what it provides.
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Sat Oct 25, 2014 3:55 pm    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

steveL wrote:
miroR wrote:
I may have not known before about that database in /var, but the tip is still just fine and completely correct!

Because that database holds only what portage installs. And I don't see another way to check on what's installed than what I suggested, apart from, sure, safekeeping the 'make install''s log.

Because it is all in make install's STDOUT, and only needs to be kept. Portage will never know about it.

This doesn't make sense to me, as it's based on a misconception. The point is that portage will install whatever the makefile installs to DESTDIR (which is a root image.)

The most that you'd have to "worry" about is the ebuild doing something customised for Gentoo. And that's all transparently in front of you in the ebuild. Hell you can just -r bump it and rework it if you want, so it's hardly obfuscated.

So, I'm not sure what problem you're trying to solve by acting as if portage is an untrusted black box, instead of just building on top of what it provides.

I said it in the first post of this topic you are reading.

I don't want to be forced to install gnupg-2, because it introduces GUI based gpgme.

I don't even have ssh-agent in Gentoo, because I have not had the need for it yet (I have it in Debian, and that one is not the problem. That one, the ssh-agent (author Daniel Robbins, the initiator of Gentoo, but missing for me in Gentoo... maybe by his own fault, really don't know)...

[That one, the ssh-agent] was previously functionally taken in by dbus in my Debian, and is so by default, with all its "remote call" non-free functionality as you pointed out in various posts of yours in the "Why is Gentoo not switching to systemd?" topic. Now that was a problem, it was, because it is now solved for me in Debian, via mirabilos' MirDebian WTF packages)...

Why is that so hard to understand? When, among other reasons, also Michael Elkins, the Mutt Dude, is, as the maintainers of Mutt in Gentoo say somewhere in the ebuilds, [paraphrasing, from memory] "uncooperative" and even "doesn't reply" to their "mails"... ?

Mutt is not meant to work with GUI programs like that, IMO.

And those introduce vulnerabilities, don't they? Three or more programming layers when one was enough, to just take in a password! Forking of something, as the discussion went about it, but on the links pointed at and explained in my "Air-Gapped Gentoo Install, Tentative" topic.

Why, oh why is that so hard to grasp? At least the last argument, how the Mutt Dude does not accept patches and neither returns replies (probably after he said it all very clearly previously)?
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)


Last edited by miroR on Sun Oct 26, 2014 12:22 am; edited 2 times in total
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2730
Location: The Peanut Gallery

PostPosted: Sat Oct 25, 2014 4:01 pm    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

miroR wrote:
Why, oh why is that so hard to grasp? At least the last argument, how the Mutt Dude does not accept patches and neither returns replies (probably after he said it all very clearly previously)?

Eh? I was only talking about the point you made about portage and make install.

Also, you don't need to quote everything, just as an aside. It only clutters the thread, and doesn't add to the conversation.
Back to top
View user's profile Send private message
Slippery Jim
Apprentice
Apprentice


Joined: 08 Jan 2005
Posts: 187

PostPosted: Sat Oct 25, 2014 11:12 pm    Post subject: Reply with quote

Just want to say to MiroR, nice job on the HOWTO. I found it very clear and easy to follow. Whether or not there's a better way to do the same thing, it's that clarity which makes it easy for people to try it out and easily compare the results against other experiments. So thanks for contributing to the community, and being positive and constructive.
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Sun Oct 26, 2014 12:16 am    Post subject: Reply with quote

Slippery Jim wrote:
Just want to say to MiroR, nice job on the HOWTO. I found it very clear and easy to follow. Whether or not there's a better way to do the same thing, it's that clarity which makes it easy for people to try it out and easily compare the results against other experiments. So thanks for contributing to the community, and being positive and constructive.

Thanx! :roll:
But see also the post below on how it should be done; and why I can't yet do it the really right way... Even though the other right way is kindly pressure the maintainers to do it for us who don't possess the know-how yet...
Maintainers, pls. get us the option to use plain gnupg-1 with portage's mutt! (But I won't send them another message in that regard. Our devs are often short with time, and really busy...)
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)


Last edited by miroR on Sun Oct 26, 2014 12:25 am; edited 1 time in total
Back to top
View user's profile Send private message
miroR
Guru
Guru


Joined: 05 Mar 2008
Posts: 390

PostPosted: Sun Oct 26, 2014 12:24 am    Post subject: Re: Install Mutt without Portage, and Why, for Air-Gappers Reply with quote

steveL wrote:
Eh? I was only talking about the point you made about portage and make install.

I see your point with the emphasis that you gave it now.
But... But I can't currently find time such as a weekend (or two or three; I'm not unintelligent, but neither top class for sure)... to study and figure out how to do it by modifying the ebuild in my own overlay. I wish soo much to be able to do that one day, even though I'm 60 in three years... I don't even understand what "...<expletive> you can just -r bump it and rework it if you want"...
_________________
Miroslav Rovis
Zagreb, Croatia
www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum