Running gpg-agent and caching the passphrase
Hi,
I'm trying to get gpg-agent running under 8.2 using the same setup I've
had on my linux box.
The agent is started via .xinitrc:
export GPG_TTY=$(tty)
if [ -z `pgrep gpg-agent` ]; then
eval $(gpg-agent --daemon --write-env-file "${HOME}/.gpg-agent-info" \
--log-file "${HOME}/.gnupg/gpg-agent.log")
fi
The agent is up and running (checked via ps) and the option "use-agent"
is set in gpg.conf. As pinentry I installed pinentry-gtk2.
If I try to sign or decrypt something the pinentry window comes up and
asks for my passphrase. So far so good but I want it to cache my
passphrase for some time.
My ~/.gnupg/gpg-agent.conf:
default-cache-ttl = 3600
But no matter what option I set the passphrase is not cached and there
is no error message in the logs.
I don't know if this is the right place to ask but the same setup was
running on my linux box without problems so I guess this might be bsd
related.
Regards,
Jens
P.S.: I use ssh-agent also and it works without problems. While using
gpg-agent with the ssh option ask for the passphrase every time the key
is used.
--
21. Wonnemond 2011, 08:24
Homepage : http://www.jan0sch.de
A crow perched himself on a telephone wire. He was going to
make a long-distance caw.
pgpTzxhv4Z7cG.pgp
Description: PGP signature
Re: Running gpg-agent and caching the passphrase
On Sat, 21 May 2011 08:34:21 +0200 Jens Jahnke wrote: > But no matter what option I set the passphrase is not cached and there > is no error message in the logs. > I don't know if this is the right place to ask but the same setup was > running on my linux box without problems so I guess this might be bsd > related. Have you considered to use (security/)keychain? It's very handy for the purpose. It's invoked by putting something like: eval `keychain --eval id_rsa your_gpg_key` in e.g. your .zshrc. Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature
Re: Running gpg-agent and caching the passphrase
On Sat, May 21, 2011 at 08:34:21AM +0200, Jens Jahnke wrote:
>
> Hi,
>
> I'm trying to get gpg-agent running under 8.2 using the same setup I've
> had on my linux box.
> The agent is started via .xinitrc:
> export GPG_TTY=$(tty)
> if [ -z `pgrep gpg-agent` ]; then
> eval $(gpg-agent --daemon --write-env-file "${HOME}/.gpg-agent-info" \
> --log-file "${HOME}/.gnupg/gpg-agent.log")
> fi
>
> The agent is up and running (checked via ps) and the option "use-agent"
> is set in gpg.conf. As pinentry I installed pinentry-gtk2.
>
> If I try to sign or decrypt something the pinentry window comes up and
> asks for my passphrase. So far so good but I want it to cache my
> passphrase for some time.
> My ~/.gnupg/gpg-agent.conf:
> default-cache-ttl = 3600
Try:
default-cache-ttl 3600
(no equals sign)
>
> But no matter what option I set the passphrase is not cached and there
> is no error message in the logs.
> I don't know if this is the right place to ask but the same setup was
> running on my linux box without problems so I guess this might be bsd
> related.
>
> Regards,
>
> Jens
>
> P.S.: I use ssh-agent also and it works without problems. While using
> gpg-agent with the ssh option ask for the passphrase every time the key
> is used.
>
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
pgpqEJsm1Lrgk.pgp
Description: PGP signature
Re: Running gpg-agent and caching the passphrase
On Sat, 21 May 2011 09:02:27 +0100 Frank Shute wrote: FS> Try: FS> FS> default-cache-ttl 3600 FS> FS> (no equals sign) Woah, stupid me. Thanks for the tip. It works now. =) Regards, Jens -- 21. Wonnemond 2011, 12:07 Homepage : http://www.jan0sch.de To be sure of hitting the target, shoot first and, whatever you hit, call it the target. pgpqz8RiWHxOA.pgp Description: PGP signature
ipv6 spam
I have begun receiving ipv6 spam from this mailing list, and I was wondering how to determine who the owner of a particular ipv6 address is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: (8.2) amd64 + linuxulator + nvidia driver is it stable ?
Le Tue, 10 May 2011 19:41:35 +0200, Patrick Lamaiziere a écrit : > Well if I still have crash, I will try with a 32 bits version. For the record, the box was not stable at all running amd64 and works perfectly in i386. I don't know why. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 spam
On Sat, May 21, 2011 at 9:28 AM, Robert Simmons wrote: I have begun receiving ipv6 spam from this mailing list, and I was > wondering how to determine who the owner of a particular ipv6 address > is. A whois may tell you who the block has been given too (ISP wise) ... that may start you in the right direction For example: I have a valid IPv6 address from my hosting provider (they gets used for IRC on occasion ..) NetRange: 2610:1E8:: - 2610:1E8:::::: CIDR: 2610:1E8::/32 OriginAS: AS14595 NetName:NET-THINKTEL6-1 NetHandle: NET6-2610-1E8-1 Parent: NET6-2610-1 NetType:Direct Allocation RegDate:2007-05-04 Updated:2007-05-04 Ref:http://whois.arin.net/rest/net/NET6-2610-1E8-1 As you can see, a whois of that ip reveals the block provided to my hosts provider, from there you could start asking questions. Spam sent to the list, I tend to ignore, spam sent to me, I investigate and make go away. I'v also run a tracert(6) to find a general geographic region of the spam, if it's origin was reasonably local then I fire e-mails off to those locations as best I can. An interesting story here ... I actually knew one of my spammers, personally, a pseudofriend who always tried to show off to me, he had money and was always buying gadgets that he had no use for or how to use. When I figured it out I almost laughed meself stupid. I then took all my proof to his Mom and it all stopped, all his gadgets mysteriously disappeared from his house and he stopped calling ... coincidentally, all of that mysteriously disappeared junk, magically appeared in my bedroom :D Anywho there are ways, just takes patience and persistence... -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: (8.2) amd64 + linuxulator + nvidia driver is it stable ?
On Wed, May 11, 2011 at 12:02:47PM -0400, Jerry wrote: > Does anyone know why the "x11/nvidia-driver" port has not been updated? Frequent ENOTIME on my side to perform all required testing. :-( > The latest version is 270.41.06 according to the nVidia page: I've updated the port few minutes ago. Sorry it took that long. ./danfe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPSec routing (long post)
Ladies and Gentlemen,
First, please excuse this extremely long post. I have tried to include
all of the information I thought was relevant, and may have included too
much.
I have established an IPSec connection to our vendor using transport mode.
However, I am having problems successfully routing the traffic. We using
a preshared key for authentication. The connection is successfully made.
My vendor has verified they are able to see the connection up on their
router and I am able to see a successful connection when running racoon in
the foreground. I am running FBSD 8.1.
My external IP address is 1.2.3.4 and the vendor's is 5.6.7.8. The
default gateway on my system is 1.2.3.5. My internal IP address range is
192.168.1.0/24 and the vendor's is 192.168.2.0//24.
Following is what I have done/tried.
Following are my entries in racoon.conf. I have not changed any of the
default settings for padding/spacing/etc.
remote 5.6.7.8
{
exchange_mode main,aggressive;
doi ipsec_doi;
situation identity_only;
my_identifier address 1.2.3.4;
proposal_check obey;# obey, strict, or claim
lifetime time 86400 secs;
proposal {
encryption_algorithm 3des;
hash_algorithm sha1;
authentication_method pre_shared_key;
dh_group 2;
}
}
sainfo address 192.168.1.024 any address 192.168.2.0/24 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 192.168.2.0/24 any address 192.168.1.024 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 1.2.3.4/32 any address 192.168.2.0/24 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 192.168.2.0/24 any address 65.1117.48.155/32 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 1.2.3.4/32 any address 5.6.7.8 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
sainfo address 1.2.3.4/32 any address 5.6.7.8 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 5.6.7.8/32 any address 1.2.3.4/32 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 192.168.1.024 any address 5.6.7.8 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
sainfo address 192.168.1.024 any address 5.6.7.8 any
{
pfs_group 2;
encryption_algorithm 3des;
lifetime time 3600 secs;
authentication_algorithm hmac_sha1;
compression_algorithm deflate;
}
The following entries are made using setkey.
flush;
spdflush;
spdadd 1.2.3.4/32 5.6.7.8/32 any -P out ipsec
esp/tunnel/1.2.3.4-5.6.7.8/require;
spdadd 192.168.1.0/24 192.168.2.0//24 any -P out ipsec
esp/transport/1.2.3.4-5.6.7.8/require;
spdadd 1.2.3.4/32 192.168.2.0//24 any -P out ipsec
esp/transport/1.2.3.4-5.6.7.8/require;
spdadd 192.168.1.0/24 5.6.7.8 any -P out ipsec
esp/transport/1.2.3.4-5.6.7.8/require;
spdadd 5.6.7.8/32 1.2.3.4/32 any -P in ipsec
esp/tunnel/5.6.7.8-1.2.3.4/require;
spdadd 192.168.2.0//24 192.168.1.0/24 any -P in ipsec
esp/transport/5.6.7.8-1.2.3.4/require;
spdadd 192.168.2.0//24 1.2.3.4/32 any -P in ipsec
esp/transport/5.6.7.8-1.2.3.4/require;
spdadd 5.6.7.8/32 192.168.1.0/24 any -P in ipsec
esp/transport/5.6.7.8-1.2.3.4/require;
Using setkey -DP all of the entries have been made.
I see the following in the log which indicates, to me anyway, the proper
policy has been applied.
2011-05-21 10:10:29: DEBUG: suitable inbound SP found: 192.168.2.0/24[0]
1.2.3.4/32[0] proto=any dir=in.
2011-05-21 10:10:29: DEBUG: new acquire 1.2.3.4/32[0] 192.168.2.0/24[0]
proto=any dir=out
2011-05-21 10:10:29: DEBUG: configuration found for 5.6.7.8.
2011-05-21 10:10:29: DEBUG: getsainfo params: loc='1.2.3.4',
rmt='192.168.2.0/24', peer='NULL', id=0
2011-05-21 10:10:29: DEBUG: getsainfo pass #2
2011-05-21 10:10:29: DEBUG: evaluating sainfo: loc='ANONYMOUS',
rmt='ANONYMOUS', peer='ANY', id=0
2011-05-21 10:10:29: DEBUG: evaluating sainfo: loc='192.168.1.0/24',
rmt=
Re: Tell a minimum requirement for RAM for virtual machines (virtualbox)
"Vladislav V. Prodan" writes: > Tell choice OS (8.2, 8.2-CURRENT or 9.0-CURRENT, FS (UFS or ZFS) and > the minimum amount of RAM for use in such schemes: > 1) the interaction of multiple routers with established quagga (bgpv4, > bgpv6, ospf) > 2) the work of two different modes of MYSQL replication servers/clusters. > 3) backup zfs partitions/snapshots to a remote server > > > Host machine - win7 64x with 6 GB of RAM That's a varied enough workload that I think you'd have to try it. ZFS has problems with low-memory conditions, so you might want to avoid it for this application. I don't think the OS version will matter much, but I'd be tempted to go with CURRENT, especially if you use ZFS. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Tell a minimum requirement for RAM for virtual machines (virtualbox)
On Fri, May 20, 2011 at 4:47 AM, Vladislav V. Prodan wrote: > Tell choice OS (8.2, 8.2-CURRENT or 9.0-CURRENT, FS (UFS or ZFS) and the > minimum amount of RAM for use in such schemes: > 1) the interaction of multiple routers with established quagga (bgpv4, > bgpv6, ospf) > 2) the work of two different modes of MYSQL replication servers/clusters. > 3) backup zfs partitions/snapshots to a remote server > > > Host machine - win7 64x with 6 GB of RAM > > Thank you for your advice. > Couple things to think about. Virtualbox by default doesn't obey flush cache commands. This is potentially a very bad thing so you'll want to look a changing the default for any ZFS VM, and probably any VM doing DB operations unless speed is more of a priority than data integrity. The other thing to keep in mind is i386 binaries use less RAM than their amd64 counter parts. For this reason, I always make my VM's 32 bit to achieve higher VM density. I have not had trouble with ZFS on i385 with 1GB+ of RAM when following the recommended tuning, but I haven't used a heavily used them either. I prefer to use the MFSBSD ZFS v28 i386 iso for the install. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Tell a minimum requirement for RAM for virtual machines (virtualbox)
21.05.2011 18:57, Adam Vande More wrote: Couple things to think about. Virtualbox by default doesn't obey flush cache commands. This is potentially a very bad thing so you'll want to look a changing the default for any ZFS VM, and probably any VM doing DB operations unless speed is more of a priority than data integrity. The other thing to keep in mind is i386 binaries use less RAM than their amd64 counter parts. For this reason, I always make my VM's 32 bit to achieve higher VM density. I have not had trouble with ZFS on i385 with 1GB+ of RAM when following the recommended tuning, but I haven't used a heavily used them either. I prefer to use the MFSBSD ZFS v28 i386 iso for the install. Thanks for the recommendation, but I have all the workers of the amd64 and tests in the i386, with its restrictions did not see the point. Now start the virtual machine to 150MB RAM, FreeBSD 8.2-CURRENT amd64 on ZFS. -- Vladislav V. Prodan VVP24-UANIC +380[67]4584408 +380[99]4060508 vla...@jabber.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Tell a minimum requirement for RAM for virtual machines (virtualbox)
--As of May 21, 2011 9:37:31 PM +0300, Vladislav V. Prodan is alleged to have said: Thanks for the recommendation, but I have all the workers of the amd64 and tests in the i386, with its restrictions did not see the point. Now start the virtual machine to 150MB RAM, FreeBSD 8.2-CURRENT amd64 on ZFS. --As for the rest, it is mine. That is quite certainly too little RAM for that setup. Lowest I've heard anyone get to with ZFS is half a GB, and it's not considered 'stable' with less than a full GB. (And from my experience I'd say you'll want more than that.) With another file system, maybe. But ZFS needs RAM. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Hardware Recovery Company
Hi, Reference: > From: Alejandro Imass > Date: Fri, 20 May 2011 11:08:21 -0400 > Message-id: Alejandro Imass wrote: > Hi folks, > > I recently sent a hard drive to be recovered and I think they just > ripped me off. I have the back-up drive and believe it or not it has > the same exact symptoms and won't mount. So I want to send both drives > to a REAL AND TRUSTED LAB for 2 things: > > 1) Forensics on the supposed head-replecement mumbo-jumbo/scam crap of > the other lab > 2) Recovery of the data of the back-up drive > > I guess this only happens once in a lifetime when both drives die, but > I can't risk the second drive to a non-certified lab. > > I really trust the people on this list so hopefully you can point me > to a real and non-bullshit lab that can really recover data. > > It would be nice to know if the lab can actually do #1 and certify my > concerns and willing to testify in court because I want to press legal > charges against the other lab if they in fact ripped me off and > jeopardized my data. But if they can't I still need to recover the > data! HELP! > > Thanks beforehand ! Announcing you'r thinking if suing the 1st rescuer, might make some people might be nervous in being 2nd rescuer. You could look at man fsdb Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, Not HTML, Not base 64. Reply below text sections not at top, to avoid breaking cumulative context. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Hardware Recovery Company
On Sat, 21 May 2011 21:14:39 +0200, "Julian H. Stacey" wrote: > Alejandro Imass wrote: > > Hi folks, > > > > I recently sent a hard drive to be recovered and I think they just > > ripped me off. I have the back-up drive and believe it or not it has > > the same exact symptoms and won't mount. So I want to send both drives > > to a REAL AND TRUSTED LAB for 2 things: > > > > 1) Forensics on the supposed head-replecement mumbo-jumbo/scam crap of > > the other lab > > 2) Recovery of the data of the back-up drive > > > > I guess this only happens once in a lifetime when both drives die, but > > I can't risk the second drive to a non-certified lab. > > > > I really trust the people on this list so hopefully you can point me > > to a real and non-bullshit lab that can really recover data. > > > > It would be nice to know if the lab can actually do #1 and certify my > > concerns and willing to testify in court because I want to press legal > > charges against the other lab if they in fact ripped me off and > > jeopardized my data. But if they can't I still need to recover the > > data! HELP! > > > > Thanks beforehand ! > > You could look at man fsdb FreeBSD offers a lot of versatile diagnostic and rescue tools, and surely fsdb is one of them. Others, provided by the base system, are "fetch -rR " and also recoverdisk. In the ports collection you'll find tools like ddrescue, dd_rescue, ffs2recov, magicrescue, testdisk, scan_ffs, recoverjpeg, foremost and photorec. And finally there is The Sleuth Kit (with its tools fls, dls, ils and autopsy). Those tools keep you from spending money to companies who also use software (this one or something else). You could also waste money on recovery programs that won't work, so trying to use the tools mentioned would be the first step. I may give two additional advices in this context: 1. Do not work with the original disk. Make a dd copy and work with the image. 2. Read about what you're dealing with. This may consume some tome, but it really helps understanding what the problem is, and therefore helps finding a solution. This is the part of the story that I know from my own desaster. :-) But as soon as you encounter hardware problems with the disk, you should try to find a recovery lab you can trust. It can be a very complicated search, and the result will traditionally also be expensive. This is the case when they can do something you can't do on yourself (e. g. disasselmbling a disk, exchanging heads in a clean-room environment) - it's mostly a matter of dealing with hardware. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Hardware Recovery Company
On Sat, 21 May 2011 14:14:39 -0500, Julian H. Stacey wrote: I really trust the people on this list so hopefully you can point me to a real and non-bullshit lab that can really recover data. Gillware, Inc. Here's a referral code as well: 13967 http://www.gillware.com/ Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Hardware Recovery Company
Hi Polytropon cc list, you wrote > > You could look at man fsdb > > FreeBSD offers a lot of versatile diagnostic and rescue > tools, and surely fsdb is one of them. Others, provided > by the base system, are "fetch -rR " and also > recoverdisk. > > In the ports collection you'll find tools like ddrescue, > dd_rescue, ffs2recov, magicrescue, testdisk, scan_ffs, > recoverjpeg, foremost and photorec. And finally there is > The Sleuth Kit (with its tools fls, dls, ils and autopsy). Could you please submit a send-pr to add that useful list to man fsdb ? (If you dont want to i would, but as you obviously know this area better ... :-) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, Not HTML, Not base 64. Reply below text sections not at top, to avoid breaking cumulative context. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Other lists exist too - Was Re: Hardware Recovery Company
For Alejandro Imass as original poster re. Hardware Recovery Company: FreebSD has a special mail list for file systeme it's name is f...@freebsd.org. (we also have hardware@ etc) For all, Questions@ started as a catch all fallback address for simple beginners questions from the newly installed, who didn't know / hadn't yet read http://www.freebsd.org/community/mailinglists.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL to find where more exactly one might ask a question. Recently questions@ seems to be performing roughly the same purpose as hackers@ list, a random jamboree/ mellange of topics, which doesnt make much sense to me (where theyre posted, not the content of the questions), I think a lot of questions@ traffic would be better posted to hackers@ or other themed @freebsd.org lists. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, Not HTML, Not base 64. Reply below text sections not at top, to avoid breaking cumulative context. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Skype with sound and video support :)
On 18 May 2011 07:56, Ion-Mihai Tetcu wrote: > On Tue, 17 May 2011 21:46:14 +0200 > Alexander Leidinger wrote: > >> On Tue, 17 May 2011 09:01:41 -0700 "Kevin Oberman" >> wrote: >> >> >> > Please put the information in this message (or at least most of it) >> > into ports/UPDATING so a few less people running old kernels will be >> > bitten by the installation of the new Skype port. >> >> And what about a wiki page? This way we can extend it in case something >> important is uncovered. > > I'm not opposed to it, but I don't see the need for it at this time. > (Plus, I'd like to keep everything inside the port - hence the longish > pkg-message - less steps to go through this way). > Wiki page is good point to look when searching internet about skype and freebsd. > -- > Ion-Mihai Tetcu > ___ > freebsd-multime...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to "freebsd-multimedia-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re: IPSec routing (long post)
>From : claudiu vasadi To : jh...@socket.net Subject : Re: IPSec routing (long post) Date : Sat, 21 May 2011 18:45:07 +0200 Some additional points: > - have you been following the FreeBSD handbook on this ? -> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html > - pls post your ifconfig interface settings > - you can use "tcpdump" to sniff traffic off of your "real" network > interface (tcpdump (-v) -i host and dst > ) > - do you have "options IPSEC" and "device crypto" in your kernel ? My understanding is the handbook was using tunnel mode to connect the networks, and I am using transport mode. Are these the same, and I am misunderstanding what I am reading. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Other lists exist too - Was Re: Hardware Recovery Company
On Sat, May 21, 2011 at 4:13 PM, Julian H. Stacey wrote: > Questions@ started as a catch all fallback address for simple beginners > questions from the newly installed, who didn't know / hadn't yet read > http://www.freebsd.org/community/mailinglists.html > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL > to find where more exactly one might ask a question. > > Recently questions@ seems to be performing roughly the same purpose > as hackers@ list, a random jamboree/ mellange of topics, which > doesnt make much sense to me (where theyre posted, not the content > of the questions), I think a lot of questions@ traffic would be > better posted to hackers@ or other themed @freebsd.org lists. Perhaps the text of the list charters in the handbook along with the short descriptions should be changed to reflect this, or at least clarify it. I have used FreeBSD for about 10 years, but I would never have thought to post to freebsd-hackers because the description is "This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. This is a technical mailing list for which strictly technical content is expected." That's a pretty scary description. I have not even subscribed to the list, let alone lurked there or posted there due to that description. That description conjures an image of DES and PHK discussing the kernel and the color of its bikeshed. Now, the freebsd-questions list has the following description: "This is the mailing list for questions about FreeBSD. You should not send “how to” questions to the technical lists unless you consider the question to be pretty technical." Now, the second sentence sounds like another do-not-disturb sign for the technical lists. So, according to the descriptions, it seems like this is the appropriate place for the jamboree. Perhaps the situation that you want is to have two lists, one for newbies, and another for the initiated. So, one solution would be to change the charter for freebsd-hackers to make it a bit less high-level. Another solution would be to create a new list freebsd- that would serve as a place to ask questions if you are not a newbie. I have a third solution. Leave everything the way it is. Having a jamboree with newbies and more versed people is good. Newbies can ask questions, non-newbies can ask questions, and importantly newbies can ramp up to answering questions they know the answer to. all in the same forum. Lastly, the description for freebsd-fs is "Discussions concerning FreeBSD file systems. This is a technical mailing list for which strictly technical content is expected." Asking for recommendations for a data recovery service (which is what the OP's message was) does not belong in freebsd-fs. The discussion may have evolved into a discussion that belongs on freebsd-fs, but that's only natural. All questions asked here will probably evolve into discussions that fit better on one of the various technical lists. In my opinion there has to be a free-for-all area where no type of questions are discouraged as you have in your message. As long as the question is about FreeBSD, it is allowed. How to eat a Yubari melon probably does not belong here, but other than keeping it to FreeBSD, I see no problems with the way it is now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
SATA Host Adapter Recommendation
I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. The highpoint cards are rated highly on newegg. Are these good with freebsd? Thanks, Jason C. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: SATA Host Adapter Recommendation
I have a Highpoint 4-port PCI-E 4x card in a server that has worked well for a few years. It's a bit pricey, but I've had no problems with it. Recently, I've gotten 3 Rosewill RC-218 cards because they're much cheaper and I don't need the RAID functionality on other cards. I'm building servers with them now, but FreeBSD recognizes the disks attached to them fine (so long as your on >= 8.2 and you add hw.hptrr.attach_generic=0 in /boot/loader.conf). I haven't tried hot-swapping any drives yet, but I'm assuming since it's SATA it should work fine. I should probably verify that soon. Rob On 5/21/11 9:26 PM, Jason C. Wells wrote: I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. The highpoint cards are rated highly on newegg. Are these good with freebsd? Thanks, Jason C. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Not able to install firefox 4 from 8.2 stable packages
I'm a struggling nooby. I am trying to install firefox 4 on a fresh 8.2 installation. I want to the core system to track the "errata" branch, and get binary packages from 8-stable (which has firefox 4). I installed FreeBSD 8.2 release. # freebsd-update fetch install rebooted # portsnap fetch extract use BASH shell # export PACKAGESITE="ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/Latest/"; installed x11 and icewm # pkg_add -r firefox get perl conflict between 5.10 and 5.12 # pkg_add -fr firefox firefox installs but I get "firefox3" instead of firefox 4.0 # pkg_info| grep firefox shows "firefox-3.6.13,1" trying to use source # cd /usr/ports/www/firefox # make install clean get errors about firefox 4.0.1 needing nspr>=4.8.7 # pkg_add -r nspr says nspr-4.8.6 or older is already installed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
