RE Benefits of Hiring Programmers:-

[Jessica]

Hi,

Hire Developers as per Requirements :-

 

*   iPhone Mobile Apps Developer
*   iPad/iPod Mobile Apps Developer
*   Android Mobile Apps Developer
*   Web Designers
*   Web Apps Developer
*   .Net Programmers
*   PHP Programmers
*   Hybrid/Native Apps Developer
*   SEO/SMO/PPC

 

Developers will work on your projects on daily basis. The Web Designer or
Developers would work 22 days a month (Excluding National Holidays in India)
and 8 hours a day devoted on your projects.

 

Benefits of Hiring Programmers:-

 

It's affordable with price as low as  nowhere in the market.
One Programmer can work on ANY number of Projects.
No Set-up Cost.
No Infrastructure Cost
You can treat Programmer as your own staff.
Programmer will have more than 4+ years of experience in their
respective field.
You can connect with Programmer directly via Email ,IMs and video
conferencing.

 

Our Key Capabilities are:-

 

*   Development of Location based Applications
*   Bluetooth Application Solutions
*   Development of Social media applications and their integration
*   Music, Picture, Videos and other sort of media integrations
*   Touch screen integration and development
*   Development of applications as per the suitability of mobile devices
and tablets
*   Improved veracity applications
*   And various others as per requirements.


Do let me know if you are interested to work with us and i am  sharing our
past work details and client Portfolio.(

http://www.appdroidsolutions.com/Portfolio.pdf.)
I look forward to your mail.

 

Thanks & Regards,

Jessica

Business Development Manager

 

 

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Mystery shopper

[Kaycee Cox]

Interested
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upcoming OpenSSL 1.1.0 release

[Lowell Gilbert]

Bernard Spil  writes:

> Today new vulnerabilities with (3)DES and BlowFish were made public

You're referring to something different than the HTTPS/OpenVPN
attacks?  Because it really wouldn't be accurate to describe those
as vulnerabilities in the ciphers.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upcoming OpenSSL 1.1.0 release

[Matt Smith]

On Aug 24 21:18, Bernard Spil wrote:
Today new vulnerabilities with (3)DES and BlowFish were made public and 
I believe we'll see release of another paper which is OpenSSL 1.1 
related with the release of OpenSSL 1.1.0. I have no knowledge if the 
paper/report contained vulnerabilities that have postponed the release 
of 1.1.0 but I think that is likely. That would mean that these 
vulnerabilities have been solved pre-release.


As far as I know x25519 is still a Draft RFC so unlikely to appear in 
browsers for a while. I can see LibreSSL adding this as well, whether 
in the draft version or in the final. This they did with 
ChaCha20/Poly1305 as well (draft in 2.3, release in 2.4). The LibreSSL 
devs would have closed the request if they didn't intend to support it 
https://github.com/libressl-portable/portable/issues/114


I don't think that FreeBSD will be making LibreSSL the 
libssl/libcrypto provider any time soon. The support timelines for 
LibreSSL (<1.5 years) are just too short for the FreeBSD release 
support (>3 years). OpenSSL is speeding up the release cycle as well 
but at least we can rely on RedHat to backport changes to older 
versions.


LibreSSL in base is a bit more than playing, it is becoming the 
default in HardenedBSD very soon and very likely in TrueOS (AKA 
PC-BSD) as of 11.0 RELEASE. Both HardenedBSD and TrueOS have a 
different attitude towards updating things in the base system as they 
do not serve as upstream to other projects/products that require 
longer support timelines. Come see my talk at EuroBSDCon, it will 
contain LibreSSL in base things.


Cheers,

Bernard.


Thanks for that reply. That answers things quite nicely. I believe 
x25519 is currently in chrome:


https://www.ssllabs.com/ssltest/viewClient.html?name=Chrome=51=Win%207=126

It has x25519 listed as an Elliptic curve near the bottom. So for that 
reason I am interested in enabling it as I like to do things bleeding 
edge! I will probably stick with security/libressl-devel for the 
foreseeable future though I think and at least wait and see what people 
make of OpenSSL 1.1 after a few months if only for the fact it's a bit 
of a pain to switch back again by recompiling everything.


--
Matt
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upcoming OpenSSL 1.1.0 release

[Bernard Spil]

On 2016-08-23 14:42, Matt Smith wrote:

On Aug 22 20:39, Mathieu Arnold wrote:

ports-committers is a *NEVER POST DIRECTLY TO* list, so, moving it to
ports@ where this belongs a lot more.

+--On 22 août 2016 20:30:15 +0200 Bernard Spil  
wrote:
| Curious to know how we should procede with the upgrade of the 
OpenSSL

| port to 1.1.0!

All ports need to work with it, I'm sure software like BIND9 do not 
build

with it.

-- Mathieu Arnold


Going slightly off-topic, I'm curious what the opinion is around this
and LibreSSL. My understanding is that LibreSSL was forked from OpenSSL
1.0.1 and they have not backported newer stuff from OpenSSL. I also
believe OpenSSL now has several full time paid developers working on it
and that the 1.1 release has some significant changes under the hood?

I've been using LibreSSL for a while so that I can get chacha20 support
but OpenSSL 1.1 will not only have chacha20, but will also have x25519
support as well. This along with what I said above is making me think 
it

might be better to go back to OpenSSL.

I just wondered what people in the know think about the current
situation with these two things. Plus are there any roadmaps for the
future of FreeBSD regarding the defaults. Is the project ever going to
look at making LibreSSL the default port, or will that be kept as
OpenSSL for many years to come? I know Bernard has been looking into
that and playing around with LibreSSL in base etc. Just curious what 
the

official policy is going to be on that.


Hi Matt,

Today new vulnerabilities with (3)DES and BlowFish were made public and 
I believe we'll see release of another paper which is OpenSSL 1.1 
related with the release of OpenSSL 1.1.0. I have no knowledge if the 
paper/report contained vulnerabilities that have postponed the release 
of 1.1.0 but I think that is likely. That would mean that these 
vulnerabilities have been solved pre-release.


As far as I know x25519 is still a Draft RFC so unlikely to appear in 
browsers for a while. I can see LibreSSL adding this as well, whether in 
the draft version or in the final. This they did with ChaCha20/Poly1305 
as well (draft in 2.3, release in 2.4). The LibreSSL devs would have 
closed the request if they didn't intend to support it 
https://github.com/libressl-portable/portable/issues/114


I don't think that FreeBSD will be making LibreSSL the libssl/libcrypto 
provider any time soon. The support timelines for LibreSSL (<1.5 years) 
are just too short for the FreeBSD release support (>3 years). OpenSSL 
is speeding up the release cycle as well but at least we can rely on 
RedHat to backport changes to older versions.


LibreSSL in base is a bit more than playing, it is becoming the default 
in HardenedBSD very soon and very likely in TrueOS (AKA PC-BSD) as of 
11.0 RELEASE. Both HardenedBSD and TrueOS have a different attitude 
towards updating things in the base system as they do not serve as 
upstream to other projects/products that require longer support 
timelines. Come see my talk at EuroBSDCon, it will contain LibreSSL in 
base things.


Cheers,

Bernard.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net-p2p/deluge now generates "ioctl sign-extension ioctl ffffffffc0206933" warnings

[Kevin Oberman]

On Wed, Aug 24, 2016 at 8:54 AM, Paul Mather <
freebsd-li...@gromit.dlib.vt.edu> wrote:

> I updated my FreeBSD/amd64 10-STABLE system yesterday to r304677.  Ever
> since, /usr/local/bin/deluged from the net-p2p/deluge port has been
> generating these messages in my system logs:
>
> WARNING pid 54659 (python2.7): ioctl sign-extension ioctl c0206933
>
>
> I rebuilt and reinstalled the port after the update just to make sure, but
> the errors still appear.
>
> Has anyone else experienced this?  Like I said, this only started
> happening for me when I updated my system to r304677. :-(
>
> Cheers,
>
> Paul.
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>

I think it's a known issue. I recall a discussion of this a few months ago,
but I still get the message from time to time. IIRC, it's python related,
as the message indicates. Note: It is not deluge that causes the error as I
don't have it installed on my system and I see the message in my
/var/log/messages now and then. Not sure if I have seen it since I
installed 11-STABLE, but saw it on 10.3.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

net-p2p/deluge now generates "ioctl sign-extension ioctl ffffffffc0206933" warnings

[Paul Mather]

I updated my FreeBSD/amd64 10-STABLE system yesterday to r304677.  Ever since, 
/usr/local/bin/deluged from the net-p2p/deluge port has been generating these 
messages in my system logs:

WARNING pid 54659 (python2.7): ioctl sign-extension ioctl c0206933


I rebuilt and reinstalled the port after the update just to make sure, but the 
errors still appear.

Has anyone else experienced this?  Like I said, this only started happening for 
me when I updated my system to r304677. :-(

Cheers,

Paul.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Matthias Fechner]

Dear all,

Am 24.08.2016 um 15:12 schrieb Lars Engels:
> I do not have *ssl from ports installed, so Icinga 2 uses the SSL
> version from base. That's why it works for me.

I face the exact same problem. I think SSL is required if you want to
talk to icinga installation on other hosts?
I personally require SSL from ports as the base SSL cannot do alpn.

But as the old 2.4.10 version worked fine with SSL port from ports,
there must be a change upstream that breaks compatibility with OpenSSL
1.0.2h?

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 03:01:53PM +0200, Lars Engels wrote:
> On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
> > 
> > Walter Schwarzenfeld  escribió:
> > 
> > ...
> > > if I remove USESßssl
> > 
> > I have openssl from ports.
> > 
> > Removed ssl from USES and yes, starts without problem.
> > Basic configuration here, logs are clean and icingaweb2 also likes it.
> 
> Strange. Thank you both for your observations!
> > 
> > Is this a PR case?.
> 
> No, I am the maintainer of the Icinga ports. :) 
> I'll try to find out why this happens.

I do not have *ssl from ports installed, so Icinga 2 uses the SSL
version from base. That's why it works for me.


pgpuA6Y7qyiz2.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
> 
> Walter Schwarzenfeld  escribió:
> 
> ...
> > if I remove USESßssl
> 
> I have openssl from ports.
> 
> Removed ssl from USES and yes, starts without problem.
> Basic configuration here, logs are clean and icingaweb2 also likes it.

Strange. Thank you both for your observations!
> 
> Is this a PR case?.

No, I am the maintainer of the Icinga ports. :) 
I'll try to find out why this happens.



pgpouJ5ZBbDWC.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Raul]

Walter Schwarzenfeld  escribió:

...

if I remove USESßssl


I have openssl from ports.

Removed ssl from USES and yes, starts without problem.
Basic configuration here, logs are clean and icingaweb2 also likes it.

Is this a PR case?.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Walter Schwarzenfeld]

Forgot to mention, I have libressl as default, maybe this causes the 
problem.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Walter Schwarzenfeld]

Cause I  only had a quick look  in  it, I have not configured it,
but
if I remove USESßssl
It seems to start (So I have eror messages, but it seems they are only  
of missing cofiguration). Please, test it.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Wed, Aug 24, 2016 at 12:17:00PM +0200, Raul wrote:
> 
> Walter Schwarzenfeld  escribió:
> 
> > This error message does not appear if I install devel/libcli.
> > But then:
> 
> Same here.

From your portmaster logfile:

===>   icinga2-2.5.1 depends on shared library: libconfig.so - found 
(/usr/local/lib/libconfig.so)

Can you try to-rebuild libconfig and then icinga2 again?



pgpYajDgxNGsc.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Raul]

Walter Schwarzenfeld  escribió:


This error message does not appear if I install devel/libcli.
But then:


Same here.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Walter Schwarzenfeld]

This error message does not appear if I install devel/libcli.
But then:
Performing sanity check of icinga2 configuration: 
/usr/local/lib/icinga2/libremote.so: Undefined symbol 
"_ZTVN6icinga18GetScopeExpressionE"

FAILED


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Raul]

Lars Engels  escribió:


WITH_PKGNG=yes

   you can savely remove this


Removed, thanks!


Do you have the output from portmaster?


https://turing.b2n.org/owncloud/index.php/s/zmFcqMX8EHEpJRl

Thanks a lot in advance.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
textproc/elasticsearch-plugin-marvel| 1.3.1   | 2.4.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Tue, Aug 23, 2016 at 09:08:48PM +0200, Raúl wrote:
> Hello!
> 
> grateful for the great work on the ports
> I don't remember last problem upgrading with them, Awesome!
> just a little setback
> 
> upgraded using portmaster, everything went apparently fine
> followed pkg-message to update schema db as I use mysql, also fine
> but when I try to start it I got:
> 
> []
> # service icinga2 start
> Performing sanity check of icinga2 configuration: 
> /usr/local/lib/icinga2/libcli.so: Undefined symbol 
> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> FAILED
> []
> 
> Not sure if I'm alone here.
> 
> this box runs 10.3-RELEASE-p6 and make.conf contains
> 
> []
> INSTALL_NODEBUG="YES"
> OPTIONS_UNSET=X11
> OPTIONS_UNSET=GUI
> BATCH=YES
> FORCE_PKG_REGISTER=yes
> WITH_PKGNG=yes
   you can savely remove this
> #WITH_OPENSSL_PORT=yes
> DEFAULT_VERSIONS+=  ssl=openssl
> []

Do you have the output from portmaster?


pgp3elJFpsNwk.pgp
Description: PGP signature